Article - CS44710
In Creo parametric mapkeys defined in the config.pro are not loaded in session when a mapkey is defined in the config.sup
Modified: 22-Mar-2023
Applies To
- Pro/ENGINEER and Creo Elements/Pro Wildfire to Wildfire 5.0
- Creo Parametric 1.0 to 9.0
- If a config.sup exists in the <loadpoint>/text directory with mapkey declarations, the config.sup will set the first mapkey entry and ignore any other setting in the config.sup for "mapkey"
- The config.sup will also override any other config.pro in the system. Therefore, only the first mapkey listed in the config.sup will be active despite mapkey declarations in the local config.pro. This is due to the fact that the config.sup file is limited to one line per option
- Items contained in the config.sup can only have one entry per option. Items that can have multiple entries, such as "mapkey", "search_path", and "def_layer" should be specified in a config.pro file
Description
- Mapkeys defined in the config.pro are not loaded in session when a mapkey is defined in the config.sup
- Mapkeys can be saved to the config.pro and work properly in session but when a new session is started the mapkeys do not operate
- Mapkeys saved to config.pro work properly in current session only
- search_path defined in config.sup are not read
This is a printer-friendly version of Article 44710 and may be out of date. For the latest version click CS44710