config.pro / mapkey.pro Creo 11 working with multiple older versions

All mapkey sequences in the config.pro file start with the word "mapkey".

So one way you could do this would be to rename their personal file to a temporary name. Read the file line by line. If the line begins with "mapkey" write that line to a new file named mapkeys.pro if not, write the line to a file named config.pro. Delete the temp file when finished.

Of course you may want to further the code to handle comment lines "!" and other exceptions.

I think I would start with that approach if it were me.

Well, I had written a fairly extensive set of steps to do this but - hit a button and lost it all!

So... you're getting the cheapo version. I would use a trail file to load the mapkey.pro file for Creo 7 and 10 (and ignore it for Creo 11). As you may know, Creo logs everything you do in a trail file. If you capture, edit, and rename that file you can reuse it whenever you wish. Once you have separated your users' config.pro files into two files (config.pro and mapkey.pro) and put them both in the startup directory, you can begin the process.

1. From a clean, new session, launch Creo 7. The config.pro file is read automatically.
2. Once Creo opens, go to File-->Options-->Configuration Editor-->Import/Export-->Import Configuration File and load the mapkey.pro file.
3. Exit Creo.
4. Navigate to the folder where your trail files are stored. Find the most recent one. Edit it to remove the "Exit Creo" from Step 3. Save and rename the file something memorable like "Creo7_Trailfile.txt" and save it in the Creo startup directory.
5. Repeat for Creo 10 creating a file with a memorable name like "Creo10_Trailfile.txt" and save it in the Creo startup directory.
6. Edit your Creo 7 & 10 startup commands (icons perhaps?) and add the full path to the trail file. When Creo launches, if you supply a trail file as an argument to the startup command, the file will run automatically upon launch.

So... if your normal startup command is something like: C:\Program Files\PTC\Creo 7.0.2.0\Parametric\bin\parametric.exe you'd simply add a space and include the path to the trail file and it would become (example):

C:\Program Files\PTC\Creo 7.0.2.0\Parametric\bin\parametric.exe  %USERPROFILE%\Creo_Startup_Directory\Creo7_Trailfile.txt

(I think the %USERPROFILE% should work to match each user's specific profile home directory but you can play with that piece).

You'd follow the same process for Creo 10 but use the trailfile for Creo 10 instead. There may not be a need for two different trailfiles but just in case, I'm presenting it this way.

Results?

Creo 7 will launch, automatically read the config.pro file, then execute the trailfile to load the mapkey.pro file. Once the trail has ended, control is passed to the user to begin work. The same would happen for Creo 10. For Creo 11, do not use the trailfile... so that the mapkeys are not read.

I'm sure this is hard to understand but you can automate this pretty easily. If you get stuck, write back and I'll try to explain further. 

Thanks!

-Brian

I don't think you need to do as much as you think you do.

Put a copy of all your mapkeys into your mapkey.pro file under the Creo 11 loadpoint text folder and remove them from the config.pro. Unless you are running ALL of your config.pro loads from an alternate common location, each Creo version has a separate text folder that have their own config.pro files. If you are running common a config.pro file, just leave the mapkeys in there after creating the mapkey.pro file. Creo 7 & Creo 10 will read the config.pro and ignore the mapkey.pro file. Creo 11 will read the config.pro and the mapkey.pro and copy the mapkeys to its ridiculous location, but it does not remove the lines from config.pro. This way Creo 7 & Creo 10 will still work with Creo 11.

Give that a try, as I don't run multiple versions of Creo to test it.