cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Mapkeys - not saving correctly, dysfunctional in different modes

Mapkeys - not saving correctly, dysfunctional in different modes

Ok, this just makes no sense at all.  I've set up my mapkeys, saved the options file, they work fine in my part files.  The minute I'm in an assembly mode, mapkeys are disabled.  That's insane becuase they behave as if I left to work outside my application.  But I'm still in Creo, just working with an assembly file.  Why would your mapkeys not apply in an assembly mode?  Simple stuff like show/hide construction planes, etc? 

UPDATE:  Ok, I finallly figured out how to fix them.  There were multiple config.pro files, one in main PTC directory, others in various project folders whenever they were the working directory, and config.pro became a horrible mess.  Creo does not save mapkeys to 1 master file, it kept saving them haphazardly to various config.pro files in differect locations, so hotkeys did not function properly.  I got rid of all config.pro files except for 1 in current working directory, and synched up all the correct mapkeys in that and master PTC location file.  They now work as expected. 

So the request for ProE here is this:  Please don't do the "save in session" mapkeys, that makes no sense.  Just have 1 master file with mapkeys applicable to all files in all directories.

4 Comments
Topaz II

Not as familiar with Creo, but do you use the exact same key strokes while in assembly mode?

Newbie

Yes, that's my point - I want to  use the exact same mapkeys, i.e. key strokes in the assembly mode. 

I have mapkeys that show/hide datums, axes, points, etc. and they work the same whether I'm in part, assembly, or drawing mode.  Unless I'm not understanding correctly, it sounds like your interface may have been customized substantially from one mode vs. another and the mapkeys are built on one of those customized interfaces. 

When I create mapkeys, I try to use commands and not interface clicks (i.e not UI tab items) if at all possible.  You can do this by temporarily adding a command to the quick access toolbar and using that to build your mapkeys.  Manually editing the config.pro may help to keep it simple.  For example, here is my "display datums" mapkey:

mapkey dd @MAPKEY_LABELDisplay Datum Planes;~ Command `ProCmdEnvDtmDisp`  0;

This toggles the display of datum planes.  What does yours look like for showing/hiding planes? 

There are circumstances where similar commands are different depending on the feature being created like edit sketch.  It's different for revolves vs. sweeps vs. extrudes, etc.  In these cases you can still create a single mapkey that edits the sketch by combining the mapkeys manually in your config.pro and setting the config option to ignore mapkey errors.  You can do the same if your interface has changed substantially from one mode to another and you can't just use the proe command.

Community Manager
Status changed to: Archived