Creo11 and Mapkey pro

Forum|Forum|1 year ago
May 13, 2024
11 replies
12449 views

We have just installed Creo 11 in our office and have now found the it is stripping the Mapkey from the Config.pro files and placing them in the App data setting folder as a new Mapkey.pro.

This is a big problem for us....

We have multiple start up shortcut that point to different folder that has different Config.pro & search.pro files depending on the task we are working on, and each Mapkey in the config.pro points to a different file location to set the working directory.

I don't have a problem with the Mapkey being placed in a separate file, but I hope we have the option in the config file to point to a different location so we can mange the different options.

Peter

Show previous replies

R

RandyJones

20-Turquoise

We just made the switch from Creo Parametric 10.0.8.0 to Creo Parametric 11.0.4.0 last week. I have since learned a couple more unexpected behaviors dealing with personal user mapkeys:

Expected: On first launch of Creo Parametric 11.0 it copies the mapkeys from config.pro to <some really hidden path>/.Settings/mapkeys.pro
- Unexpected: Any conflicting user mapkeys (eg same name) as the system mapkeys.pro are NOT copied into the .Settings/mapkeys.pro file
- So we then manually edited the .Settings/mapkeys.pro and add the conflicting mapkeys
  - We actually just copied the config.pro, which was mapkeys only, into .Settings/mapkeys.pro
  - So now we have mapkeys that conflict with the system mapkeys.pro
- Refired up Creo Parametric 11.0
- Unexpected: The conflicting mapkeys in .Settings/mapkeys.pro are not read.
  - This is different behavior than pre Creo Parametric 11.0 in which the last one read was the winner
  - So it currently is impossible for the user to override mapkeys contained in the system mapkeys.pro when launching Creo Parametric
  - They need to rename these conflicting mapkeys
- Expected: From the new mapkeys editor doing a manual import of the .Settings/mapkeys.pro overrides any existing mapkey.

So depending on how you want to look at this the inability for the user personal mapkeys to overwrite system mapkeys is either:

Yay its about time this happened!
or This really sucks and needs to be fixed!

M

MartinHanak

24-Ruby III

@RandyJones wrote:

We just made the switch from Creo Parametric 10.0.8.0 to Creo Parametric 11.0.4.0 last week. I have since learned a couple more unexpected behaviors dealing with personal user mapkeys:

Expected: On first launch of Creo Parametric 11.0 it copies the mapkeys from config.pro to <some really hidden path>/.Settings/mapkeys.pro

Unexpected: Any conflicting user mapkeys (eg same name) as the system mapkeys.pro are NOT copied into the .Settings/mapkeys.pro file

So we then manually edited the .Settings/mapkeys.pro and add the conflicting mapkeys

We actually just copied the config.pro, which was mapkeys only, into .Settings/mapkeys.pro

So now we have mapkeys that conflict with the system mapkeys.pro

Refired up Creo Parametric 11.0

Unexpected: The conflicting mapkeys in .Settings/mapkeys.pro are not read.

This is different behavior than pre Creo Parametric 11.0 in which the last one read was the winner

So it currently is impossible for the user to override mapkeys contained in the system mapkeys.pro when launching Creo Parametric

They need to rename these conflicting mapkeys

Expected: From the new mapkeys editor doing a manual import of the .Settings/mapkeys.pro overrides any existing mapkey.

So depending on how you want to look at this the inability for the user personal mapkeys to overwrite system mapkeys is either:

Yay its about time this happened!

or This really sucks and needs to be fixed!

Hi,

from my point of view, the implementation of mapkeys.pro in Creo 11.0 is inappropriate. I do not understand why PTC did not use following paths.

Creo_loadpoint\Creo 11.0.x.0\Common Files\text\mapkeys.sup ... these mapkeys could not be overwritten
Creo_loadpoint\Creo 11.0.x.0\Common Files\text\mapkeys.pro
HOMEDIR\mapkeys.pro
STARTDIR\mapkeys.pro