I could use some help. I am evaluating Creo 1.0, M020 Datecode. We currently use a global config.pro combined with a local (user) config.pro. While in the configuration editor, is there a way to just view the local config.pro and export just the local if changes are made? Previous versions let you pick the file displayed by local or global with a file path.
I would like to know the answer to your question, too.
BTW, I think in Creo 1.0 it is not possible to distinguish the content of config.pro files loaded during startup.
If I understand correctly try unchecking the 'show current session option' in the 'display filter' (see attached)
I tried turning off the "show current session" in the display filter. The problem is when I export the config.pro, I get the the combined options of the global config.pro, default.pro (sup) and and my local config.pro. It doesn't see to distinguish between local, load point and system default when you export--it combines them all into 1. Previous versions did not have this issue and could easily toggle between the different files and save. I can work around it by exporting to a different directory and editing the config.pro with notepad to carve out the non-local options.
I don't know if this is an oversight or there is a specific reason this is occurring.
When launching Creo I already have customer specific config files loaded in the working directory. I normaly save working directory config files (if changes are needed) with the 'show current session' ticked. I save the changes to the working directory, and when doing so I see no changes occurr to the config files in global load point.
Where are your local config files loaded?
in Wildfire 5.0 and also in Creo Parametric 1.0 you can use config.pro files located in three directories:
Inside Wildfire 5.0 you can edit any of these files individually.
Creo Parametric 1.0 merges these files into one and you have no chance to separate them.
Checking with 'system information' (see below) suggests that when launching Creo Parametric 1.0 it still reads seperate config files during a program start.
Hopefully we will have the "old" functionality back on a later release as my loadpoint\text config.pro has a lot of options that are hard to wade through. I use a lot of mapkeys and other specific settings for effcicieny and prefer to save these back to my startup config.pro. I guess for now, the copy and paste or manual add tecnhique will need to be used.
I just want to know the reason for the change.
Open a call with PTC and have them add your call to SPR 2095853. Ability to view and save options loaded from different configuration files is lost in Creo Parametric 1.0.