Skip to main content
Apr 11, 2013 7:58 PM UTC
Delivered

An Option in Config.pro to specify a separate file for Mapkeys

Related products:Creo Parametric

A highly customized Config.pro file can be confusing to manage and can become cluttered with duplicate entries - for both mapkeys and options.   An option to specify a separate mapkey file would make managing these files much easier.

This is even more important since the ability to have multiple sessions has been added.  This would enable using different config.pro files for different sessions and easily use the same mapkeys.

Regardless of the many possible post-installation work-arounds, this out-of-box solution would save a lot of (especially first time) users a lot of headaches.

19 replies

Dec 14, 2022 5:08 PM UTC

Yes @BenLoosli

 
This is exactly as I imagined the implementation...if a Config contained a 'Mapkey_File_Path' (your good name for it - or perhaps just Mapkey_File), then it would read the external  file of Mapkeys.  Mapkeys that might already be in the Config file would be retained.  The external file Mapkeys that are unique would be added to the available Mapkeys.
 
A question arises about what to do with duplicate (un-unique) Mapkeys in the external file...should they be ignored...or should they override Mapkeys already existing in the Config?  Personally, I'm for the 'ignored' solution...this would allow a convenient way for administrators to maintain adherence to certain Mapkey standards, while enabling individuals or groups to easily add and maintain their own.
 
For a majority of users, Configs would contain no Mapkeys...so that all Mapkeys are established and maintained (edited) in the external file (separating them from the current messy environment of Config files).
 
Years ago I explored keeping each individual Mapkey in its own file (in my case suffixed with .mpk) and using a batch file to concatenate all the *.mpk files into a file and then concatenating that into the config.pro (like @NicolasBourgeoi1 indicates above).  This may sound like a great method - as you can save just individually created Mapkeys to a single file (and then rename them with the .mpk suffix).  This works well...until PTC issues a update that requires changing (manually editing) most of the over 400 Mapkeys I developed and depend on over the years.   In this case, it's best to have all the Mapkeys (or at least most) in a single file.
 
To permanently implement a manually edited Mapkey requires exiting Creo and restarting.  There needs to be a way to re-read the Mapkeys into a session without having to completely exit the program.  A separate Mapkey file/s would make this functionality easier.  But this capability will undoubtedly require submitting another new idea request.
 
I like the idea of being able to read 'Mapkey_File' multiple times, or perhaps a comma-separated list of files.  This would allow Mapkeys with similar functions to be nicely grouped and managed.
 
And all of this complicates (or at least affects) user interface modifications (for those that use mapkeys from the ribbon), but this can be managed reasonably with a little planning.
 
As a matter of note:  Mapkeys should not be thought of as just 1 or 2 or 3 key-hit shortcuts.  'Long-name' Mapkeys can be directly accessed from the ribbon, and can be called from within other Mapkeys.  Mapkeys (actually 'Macros') can be a powerful tool.  Nesting Mapkeys  can multiply that capability.
Feb 15, 2024 2:46 PM UTC

Is there any update on this?

We wanted to add personal macros to centralized config pro... I'll use one of previous workarounds, but would be useful a managing panel

 

Feb 15, 2024 3:22 PM UTC
Status changed to: Implementation In Progress
Feb 16, 2024 1:05 PM UTC

@mneumueller Can you comment on how this is being implemented? If a company config.pro points to a mapkey file but then a user also has the same config pointing to a different mapkey file does the company mapkeys get overridden?

Feb 16, 2024 2:09 PM UTC

you can have mapkey files on admin and user level.
They will both be loaded and be shown separately in the UI.

mneumueller_0-1708092452775.png

You will be able to test some of this in the Creo 11 beta test starting Feb 26. 

To register use the link : https://www.ptc.com/en/products/creo/beta/

 

 

Apr 18, 2024 1:10 PM UTC
Status changed to: Delivered

this is delivered with Creo 11 - Enhancement: Separate Mapkeys Configuration

 

Oct 30, 2024 4:12 AM UTC

Sorry Team, I would love to understand why a product manager would choose to copy the mapkeys from a config.pro file in the start_dir to a user profile location %USERPROFILE%\AppData\Roaming\PTC\ProENGINEER\Wildfire\.wf\.Settings, rather that the same start_dir. You did a great job from an admin perspective in the load_point. This really is a step backwards, how do i now update mapkeys at a project level for hundreds of users. Please take user profiles out of the search path.

 

Article - CS416002 - Is it possible read Mapkeys.pro from Start-in directory in Creo Parametric 11.0 works to specification............

 

Oct 30, 2024 10:25 AM UTC

The product definition team continued to look into this and we plan a further refinement  towards allowing settings to load mapkeys from the run directory.    Along with that we would restrict to load the  .ui  simultaneously from both, the run directory and the user directory (which was possible previously if load_ui_customization_run_dir was set to yes)

Oct 31, 2024 1:44 PM UTC

Elated that a 10 year old idea has been delivered, I anxiously separated out my nicely organized 800+ mapkeys into a mapkeys.pro file intuitively saved in my startup directory.  By 'nicely organized', I offer the following brief example...

 

mapkey ta @MAPKEY_LABELToggle Axis Display;\
mapkey(continued) ~ Command `ProCmdEnvAxisDisp` 1#done-return;~ Command `ProCmdViewRepaint`;

 

mapkey tc @MAPKEY_LABELToggle Coordinate Display;\
mapkey(continued) ~ Command `ProCmdEnvCsysDisp` 1#done-return;~ Command `ProCmdViewRepaint`;

 

mapkey td @MAPKEY_LABELToggle Datum Planes;~ Command `ProCmdEnvDtmDisp` 1;\
mapkey(continued) #done-return;~ Command `ProCmdViewRepaint`;

 

mapkey tf @MAPKEY_LABELOpen Family Table;@MAPKEY_LABELFamily_Table;\
mapkey(continued) ~ Command `ProCmdMmFamTab`;

 

mapkey tp @MAPKEY_LABELToggle Point datums;~ Command `ProCmdEnvPntsDisp` 1;\
mapkey(continued) #done-return;~ Command `ProCmdViewRepaint`;

 

These are 'slimmed down' (edited) from the version created by the version of Pro-E that I was using at the time.  They simply toggle the display of different datums, and 'tf' (I had already used 'ft' for another mapkey) opens the family table for a part or assembly.

 

There's a space between each mapkey, just as I had my config.pro file organized.  In the new mapkeys.pro file, there is no way to conveniently maintain spacing, which makes adding/creating, modifying/editing, troubleshooting much more difficult, let along being located in a 'non-intuitive' directory.  Though it might take a few more bytes to save the file with spaces, I don't expect it would take significantly longer to load...but is much easier to understand and modify.

 

Imagine my frustration as edits to my newly featured separate mapkeys.pro file had no effect (my fault for not thoroughly reading the description of the new capability).  So now I have another shortcut on my desktop that opens the file, though it took a little finesse to create a shortcut to a file in a directory that is normally not accessed.

 

I guess I shouldn't have assumed that a separate mapkeys file would naturally and logically be located in the same directory as the previously applicable startup config.pro file.  Otherwise I would have described it that way in the proposed product idea.