Skip to main content
May 13, 2024 2:48 PM UTC
Acknowledged

Mapkey config.pro

Related products:Creo Parametric

Please include detailed documentation such as screenshots, images or video.

1. What product and version are you running?
Creo Parametric 11


2. What is the problem?
Unable to use customer specific mapkeys without loading ALL mapkeys.

3. Are you using a workaround? If yes, please describe it.
Currently in versions prior to Creo 11, we put customer specific mapkeys in a localized congig.pro. 

4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.
I would like to see a config.pro setting to point to a local mapkey file that can be used for customer specific mapkey settings that are different from the default ones.

5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)
Impact is about 10 minutes for each time we may need to restart Creo after switching/renaming the mapkey.pro file for each customer.

11 replies

May 13, 2024 8:19 PM UTC

I have posted the below as a reply to my comment in  another post, but it sums up our needs

From my Original post....

 

 

I can see what PTC is trying to do, but that isn't any help for how we are using Creo...

 

As we use Creo to manage a production plant with forging equipment , product design and CNC machines , we have found the best way to manage our operation is to have Program start shortcut that point to Creo, but with the option to start in a specific folder based on the session we are starting, not the user.

 

We have for each type of operation , a separate start shortcut, see below.

Wheelsofsteel_0-1715631504328.png

 

in this short cut, we point to a folder that stores our search.pro & config.pro files for the type of session we are about to open.

 

Wheelsofsteel_1-1715631504468.png

 

  

Wheelsofsteel_2-1715631504330.png

 

 

 

This works fine for us, as we found trying to had one search pro & config pro files wasn't a good idea, as it was trying to load everything into memory, so this arrangement allowed us to have session based setup for the task we are doing.

 

This include Mapkey that was setup based on the sessions needs, like setting the working directory and other folder locations for the tasks we are about to do.

 

All we need is to have an option in the config.pro to set where the Mapykey. Pro file is stored, like everything else, this will give us the flexibility to manage the mapkey based on the session started, and not who the user is.

 

I hope this is fixed in future releases of Creo 11, otherwise it is a step backwards for us.

 

Peter 

olivierlp
Community Manager
May 16, 2024 1:34 PM UTC
Status changed to: Acknowledged

Thank you @BenLoosli for your idea and @Wheelsofsteel for the comment. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.

Olivier
Oct 29, 2024 11:33 AM UTC

Yes this NEEDS to happen.

 

This very issue is stopping us from moving up to Creo 11. 

 

Definitely a step backward . 

Dec 18, 2024 2:02 PM UTC

We need the ability to specify locations for both the Admin mapkeys.pro file and the user mapkeys.pro files are located from the config.pro file.

We sometimes do work for other companies and need to use their configuration and mapkeys.

 

Feb 25, 2025 8:16 PM UTC

There needs to be config.pro setting that points to the location of the mapkey.pro.  How this was over looked and the fact that its going to be buried in a hidden users App data folders is crazy.

Feb 25, 2025 8:45 PM UTC

We need the ability to manage multiple mapkey files, similar to how we manage multiple config.pro files.

Mar 10, 2025 11:01 PM UTC

I don't see how MOVING the mapkeys out of the config.pro file is an enhancement. I do agree with being able to have a separate mapkeys.pro will be handy. But it should not force them to be removed and placed in the Roaming setting directory. There needs to be a config to specify what file to read to load additional mapkey information. This change will make it very difficult for us to be able to run both Creo 10 & Creo 11 without having different working directories just extra work and confusion for users. I wish PTC would discuss changes with the public before making changes that could negatively affect customers. 

 

Maybe PTC should have to post their ideas (with very specific details) and allow us to vote on them before they get implemented.

Apr 15, 2025 8:21 PM UTC

I need to retract some of my previous statements. I have tested again and found that Creo does not strip the mapkeys from the config.pro files..It is possible to run both Creo 10 & Creo 11 with the same startup folder and config.pro file. Just have to deal with the annoying dialog boxes in Creo 11. The last two can be set to do not show in future.

WayneSchrock_0-1744747717850.png

WayneSchrock_1-1744747753062.png

WayneSchrock_2-1744747767408.png

 

 

 

Apr 15, 2025 8:26 PM UTC

Wayne,

What build of Creo 11 do you have installed.  Just curious if PTC made a change recently to Creo 11.

Apr 15, 2025 8:51 PM UTC

11.0.3.0