Skip to main content
DomenicLaritz
DomenicLaritz16-Pearl
16-Pearl
February 15, 2021
Solved

Overwriting mapkeys

  • February 15, 2021
  • 3 replies
  • 19885 views

Hello CAD admins,


you probably also provide your users with a company-config.pro with standard mapkeys in the text directory of the Creo installation.
In our case it happens again and again that users create their own mapkeys (which is legitimate), but when saving them they manage to write out the complete company-config.pro into the local one in the home or start directory.
Since the local mapkeys have the sovereignty, the users do not get changes to the mapkeys in the company-config.pro anymore.
As far as I know, the default mapkeys can't be packed into a config.sup either, because then the users can't create their own mapkeys anymore.
How do you deal with the problem of overwritten default mapkeys?

 

Regards,

Domenic

Best answer by Chris3

We have a header / footer in our config.pro and then our startup script checks for that header and if it finds it, deletes everything until it gets to the footer (ie deleting the company config out of the user config)

 

! ++++++++++ START OF COMPANY CONFIGURATION FILE. ++++++++++

! IF YOU SEE THIS IN YOUR PERSONAL CONFIG.PRO DELETE FROM THE LINE ABOVE TO WHERE IT SAYS END.
!=================================================
!Max number of characters per row is 80 although mapkey(continued) doesn't count
!2345678901234567890123456789012345678901234567890123456789012345678901234567890
!=================================================
!mapkey(continued)12345678901234567890123456789012345678901234567890123456789012345678901234567890

! ++++++++++ END OF COMPANY CONFIGURATION FILE. ++++++++++

3 replies

S
23-Emerald III
StephenW23-Emerald III
23-Emerald III
February 15, 2021

There were a few releases of Creo 4 that had the issue of always saving the entire "session config" to the user config.pro, since we moved past that, I haven't noticed that problem recently.

 

 

DomenicLaritz
DomenicLaritz16-PearlAuthor
16-Pearl
February 16, 2021

That's an interesting fact that I didn't know.
Do you have more detailed information on this, such as a CS article or an SPR number?

tbraxton
22-Sapphire II
tbraxton22-Sapphire II
22-Sapphire II
February 15, 2021

In the context of using a config.sup with mapkey definitions two items are of interest in this context.

 

Excerpt from:

https://www.ptc.com/en/support/article/CS44710 

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

This reads such that the users can overide config.sup mapkeys for the current session only. It would force them to manually save a local config.pro with mapkeys each time Creo is launched. This would prevent users from missing out on administrative changes to the config.sup without intentionally overriding them for each Creo session. I have not tested this.

 

There are also tools to detect mapkey mnemonic conflicts.

 

You could write a script that scans user local config.pro for mapkeys that conflict with corporate standards and either notify them and/or delete the conflicts in their config files in an automated fashion.

Chris3
Chris321-Topaz IAnswer
21-Topaz I
February 15, 2021

We have a header / footer in our config.pro and then our startup script checks for that header and if it finds it, deletes everything until it gets to the footer (ie deleting the company config out of the user config)

 

! ++++++++++ START OF COMPANY CONFIGURATION FILE. ++++++++++

! IF YOU SEE THIS IN YOUR PERSONAL CONFIG.PRO DELETE FROM THE LINE ABOVE TO WHERE IT SAYS END.
!=================================================
!Max number of characters per row is 80 although mapkey(continued) doesn't count
!2345678901234567890123456789012345678901234567890123456789012345678901234567890
!=================================================
!mapkey(continued)12345678901234567890123456789012345678901234567890123456789012345678901234567890

! ++++++++++ END OF COMPANY CONFIGURATION FILE. ++++++++++
    joe_morton
    18-Opal
    joe_morton18-Opal
    18-Opal
    February 16, 2021

    Does the company config file always get saved in the user's config as a single block? i.e., the users' settings don't get mixed inside the company settings? 

     

    That is a really cool idea! I've wanted to develop code for that, but I though I'd have to check each config setting.

    DomenicLaritz
    DomenicLaritz16-PearlAuthor
    16-Pearl
    February 16, 2021

    I have just found a suitable product enhancement idea from 2016 for my problem:

    "Allow Mapkeys in both config.sup and config.pro"

     

    Maybe you can support my request and push the idea with your vote - thanks in advance for your support!

      DomenicLaritz
      DomenicLaritz16-PearlAuthor
      16-Pearl
      May 8, 2024

      The product enhancement idea now has the status "Delivered".
      According to @mneumueller there came a solution for this problem with Creo Parametric 11.0: https://community.ptc.com/t5/Creo-Parametric-Ideas/Allow-Mapkeys-in-both-config-sup-and-config-pro/idc-p/944496/highlight/true#M20691 

      Terms & ConditionsAccessibility statement