Skip to main content
K
Karoly10-Marble
10-Marble
July 10, 2025
Solved

Is there a way to permanently overwrite a mapkey in Creo 11 Education version?

  • July 10, 2025
  • 3 replies
  • 1273 views

I received a config.pro file containing mapkey settings. Some of them work, while others don't execute the intended commands. If I manually set the command via Creo → Options → Mapkeys Settings, it works, but it doesn’t allow me to save the changes, so the old command is active again after restarting the software. Exporting and importing didn’t help either.

The command was assigned to the vb keyboard combination, and I tried to set it to the View Bottom orientation.

Is it possible to overwrite an existing mapkey so that it persists after restarting Creo, or can only unused keyboard combinations be reliably assigned for this purpose?

Best answer by Karoly

ChatGPT helped me solve the problem. The config.pro file in the startup directory is not the primary one, which is why I couldn't change the commands with it. Now that I’ve replaced both config.pro files, the previous mapkeys settings are gone.

 

Creo processes the config.pro and keymap.pro files based on the following load order:

 

text\config.pro in the Creo installation directory (admin level)
start\config.pro if such a file exists
config.pro in the user directory (this can be used as a personal configuration)

3 replies

K
KenFarley21-Topaz II
21-Topaz II
July 10, 2025

You don't specify what version of Creo you are using. This is particularly important in this case because they changed how mapkeys are stored in the latest version (versions?) of Creo. In later versions they are stored in a separate file, "mapkey.pro".

If you're reading this you can take a look to the right and you'll see that the forum has "Recommendations" that it thinks pertain to your topic. You might want to have a look at some of those posts and you'll likely get an idea of how to do what you wish. In essence you'll want to replace the mapkey commands you want to modify in whatever file they are stored in. Then the next time you start Creo it will load the new mapkey and you'll be all set. When you change the mapkey in a session it is only for the duration of that session.

K
Karoly10-MarbleAuthor
10-Marble
July 10, 2025

It was in the title PTC Creo 11 Education version. 🙂

 

tbraxton
22-Sapphire II
tbraxton22-Sapphire II
22-Sapphire II
July 10, 2025

Creo 11 requires the use of mapkey.pro file to load and store mapkeys. Delete the mapkeys from your config.pro file. Create a new mapkey.pro file and set up Creo such that the mapkey.pro file is loaded when Creo is started.

 

Enhancement: Separate Mapkeys Configuration

K
Karoly10-MarbleAuthor
10-Marble
July 10, 2025

Deleting the mapkeys file does not help; I cannot delete these administrator mapkeys. They can be individually overwritten, but after restarting, the unwanted commands return.

Dale_Rosema
23-Emerald III
Dale_Rosema23-Emerald III
23-Emerald III
July 10, 2025

I know it's the administrator, but I don't think I have every used 1 or 2 keystroke mapkeys since they execute at the entry of that one two key(s).

Typically I use 4 (max) key strokes and typically they are mostly left handed since I am a right handed mouser.

 

For instance, your "w" mapkey I would change to "wwww" for the measure command.

K
Karoly10-MarbleAuthorAnswer
10-Marble
July 10, 2025

ChatGPT helped me solve the problem. The config.pro file in the startup directory is not the primary one, which is why I couldn't change the commands with it. Now that I’ve replaced both config.pro files, the previous mapkeys settings are gone.

 

Creo processes the config.pro and keymap.pro files based on the following load order:

 

text\config.pro in the Creo installation directory (admin level)
start\config.pro if such a file exists
config.pro in the user directory (this can be used as a personal configuration)

    B
    23-Emerald III
    BenLoosli23-Emerald III
    23-Emerald III
    July 10, 2025

    With Creo 11, any mapkeys in the config.pro get copied to a local folder. If you edit the mapkey in that local folder, it will overwrite any admin defined mapkey defined in the mapkey.pro file in the <loadpoint>/text folder. This will not work if the admin still uses the config.pro to store the mapkeys.

    Terms & ConditionsCookie settingsAccessibility statement