de re Mapkeys

Generally, this document is about Mapkeys, and not a place to collect mapkeys. I think the place to collect mapkeys is a Mapkey Index document and separate documents for each mapkey/mapkey group. For example, the rather lengthy mapkeys should get their own documents, but one liners that do pan-zoom-rotate, for example, can get their own.

Beginning

Start with Olaf Corten's suggestion (from use of "main_dlg_cur" command for mapkeys -- from Wildfire5.0 to Creo1.0)

Use this config.pro option: cmdmgr_trail_output YES  (before starting recording)

Your ProE trail file then consists mostly of commands like these

    ~ Command `ProCmdModelOpen`

instead of

    ~ Activate `main_dlg_cur` `File.psh_open`

Further Olaf smarts (use of "main_dlg_cur" command for mapkeys -- from Wildfire5.0 to Creo1.0)

1. Open the config.pro with a text editorset the config option cmdmgr_trail_output YES and save the config.pro
2. (re)start ProE
3. find all mapkeys with "main_dlg_cur" commands (e.g. ~ Activate `main_dlg_cur` `File.psh_open` )
4. Update them manually: perform the same mapkey step(s) in ProE
5. open your trail file with a text editor
6. look at the latest added lines at the bottom (e.g. ~ Command `ProCmdModelOpen` )
7. Replace the "main_dlg_cur" commands with the "~ Command" commands in the config.pro.
8. And while you're at it: remove all ~Select - ~ Close combinations. They're not needed.
9. Save the config.pro Or Re-Record them:

Open the Mapkey dialogue

Pre-Creo1: Tools-> Mapkeys-> [select mapkey]-> Modify-> Record

Creo1: File-> Options-> Environment-> Mapkeys Settings-> [select mapkey]-> Modify-> Record

Now perform the same mapkey step(s) in ProEStop the recording and save.    

(Note when re-recording them you will get duplicate mapkeys in your config.pro. The last one will be the newest.) 

This is a spreadsheet that is said to have a bunch of mapkeys in it from Mike Foster- I have not checked them recently enough to remember, but I must have looked at them at one time.

(use of "main_dlg_cur" command for mapkeys -- from Wildfire5.0 to Creo1.0)

Advanced Mapkeys

One feature that has been mentioned as handy is that bad commands in mapkeys are simply rejected. So one can build a mapkey that works on parts and fix into it parts that work on assemblies and the command interpreter will ignore the part that doesn't apply. SeeStrategies to implement multi mode mapkey functionality

A hint to making a more universal mapkey: Re: Mapkey difficulty with Creo UI across modes

from Jose Costa

In selecting the results from the Find tool, to select all of them, it may be useful to replace what looks like the list item with a universal reference

Replace the line

mapkey(continued) ~ Select `selspecdlg0` `ResultList` 1 `7:52:`

with

mapkey(continued) ~ Select `selspecdlg0` `ResultList` -1; \

Mapkeys for selection filters

See Useful mapkey for changing the selection filter

Mapkey Cautions

Re: Mapkey best practices in Creo

When mapkeys from older versions are still functioning in later versions, it usually means that there was no change in this area.

However, in some rare cases they trigger a mechanism, that loads small parts of the old user interface, to enable the mapkey successfully processing.

These parts of the old UI will usually persist in a session and can alter the UI for this function even when the user is manually selecting menus.