Add processing of <UserHome>/creo_parametric_customization.ui

[bpavon-2]

In Pro/ENGINEER Wildfire 4 and earlier, GUI customizations were defined in the config.win file. Just like with the config.pro file, multiple instances of this file were potentially read if they existed. The possible instances were:

1. <ProEHome>/text/config.win
2. <UserHome>/config.win
3. <LaunchPath>/config.win

In Creo Parametric 2.0, the config.pro file is still processed this way. The GUI customization files processed are:

1. <CreoHome>/Common Files/text/creo_parametric_admin_customization.ui
2. (<LaunchPath>|<WorkspacePath>/.Settings)/creo_parametric_customization.ui (which one is read is controlled by config.pro option load_ui_customization_run_dir)

The request is to add processing of <UserHome>/creo_parametric_customization.ui prior to processing of (<LaunchPath>|<WorkspacePath>/.Settings)/creo_parametric_customization.ui. This file is intended to be used for site preferences which when changed will not require changes to <CreoHome>.

[dgschaefer]

I'd expand you idea and say make it work just like the config.win did.  Differences:

1. Only loads from the cache, deep in the user's Windows profile*.
2. Doesn't load from the 'start in' folder*.
3. Doesn't load from the user's home folder.
4. Saves without asking me

I'd rather have it easily accessed and predictable, just as it was.  Now it's buried and gets updated without me knowing it.

A config option could be added for #4 to choose if Creo will save the file automatically.

*There's a config option to force Creo to load the *.ui file from the working directory, but, because of #4 changes are likely to end up being saved to multiple *.ui files in multiple working directories.

[bpavon-2]

Hi Doug,

I thought I was asking to make it work very similarly to config.win. In our environment we use wrapper software to start Pro/ENGINEER (currently Wildfire 4) off a server-resident location. The wrapper software creates config.pro, config.win and menu_def.pro files in the user's home directory which contain our site preferences. It also always uses a standard location (<UserHome>/pro) as the launch directory.  We are in the middle of porting from Wildfire 4 to CreoParametric 2.0. We have the wrapper software ported. We are using "load_ui_customization_dir yes" so that the user creo_parametric_customization.ui file will be read from the launch directory. This request is to allow us to use a site creo_parametric_customization.ui residing in <UserHome>.

The request has nothing to do with how the user's creo_parametric_customization.ui is saved from CreoParametric. I am aware of the issue of the file being saved without prompting in whatever happens to be the current directory (when "load_ui_customization_dir yes:"). This issue should be dealt with as a separate request.