Customization.ui

I've found with an externally loaded file it doesn't recognise it first time, you have to Import it from the menu customisation window then it fixes, make sure you apply all customisation or it will only apply to the current interface.

I ended up making a little list of all the environments I work in as the customisation is seperate for each one, this is good once your up and running as each interface has different prioritites but is a bit time consuming initially, even part mode in the asm (RMB > Activate) has its own interaface,

Don't forget to add in the config line:

load_ui_customization_run_dir YES

Without this it won't read the file.

In Reply to Brad Mozley:

Creo Community,

I just installed build M050, and normally I copy my customization ui
file (creo_parametric_admin_customization.ui) to :

C:\Program Files\PTC\Creo 2.0\Common Files\<build>\text

This is not working. Any ideas?

Brad

This is not necessary. It also looks like a big time sink.

Try this:

1. Create the customization you'd like to use. You'll have to do this separately with each mode. (You said you have many different customization files already created. I'm not sure if you can simply load these sequentially or if you'll have to recreate a single customization.ui that incorporates each mode.)

2. Once each mode is customized the way you'd like, export the .ui file. Place it in your Start In directory. (Alternatively, if it's going to be used company-wide, rename it to creo_parametric_admin_customization.ui and put it in the load directory's \text folder.)

3. Add a config line: 'load_ui_customization_run_dir YES'

Now when you launch, it will pick up the new ui. No need to load up a bunch of customization.ui file every time you launch.

In Reply to Sean Kerslake:

I've found with an externally loaded file it doesn't recognise it first time, you have to Import it from the menu customisation window then it fixes, make sure you apply all customisation or it will only apply to the current interface.

I ended up making a little list of all the environments I work in as the customisation is seperate for each one, this is good once your up and running as each interface has different prioritites but is a bit time consuming initially, even part mode in the asm (RMB > Activate) has its own interaface,

Since he had already mentioned he gave it the correct admin name, I didn't bother to point this out.

Since we WindchillPDMLink instead of working folders, this is something I had not encountered. Sounds like it's working similar to many other functions Pro/E has always done with regards to working folders. Not the most well thought out situation from PTC.

In Reply to Doug Schaefer:

I believe that it should read the creo_parametric_admin_customization.ui file from the text folder regardless of that config setting.

There is a problem with that setting, but it may not matter to you depending on how you work. This tells Creo not only to load the creo_parametric_customization.ui from the working directory, but to save it there as well. The problem comes when you change your working directory during the day.

You launch Creo with folder A set as the start in folder. The creo_parametric_customization.ui file found there loads at startup. You then change your working directory to folder B, your project folder, and begin your work. Along the way you add an icon to the quick access toolbar, prompting an automatic save of the creo_parametric_customization.ui file into folder B. Tomorrow, when you launch Creo, your new icon is not in the quick access toolbar because your creo_parametric_customization.ui file was not saved to the startup folder, folder A. Not to mention that you end up with creo_parametric_customization.ui files in all your project folders and if users share folders they overwrite each other's creo_parametric_customization.ui files.

--

No. It's my understanding that if you copy the admin .ui file into the correct folder - usually /text - AND you have the config.pro option set correctly, it will load it without issues. It's been around 6 months since I was testing this, but unless my memory is failing me it worked just fine once the config option was in place. No need to load it every time.

In Reply to Doug Schaefer:

Is this always the case with newly copied files? I plan on creating a creo_parametric_admin_customization.ui file and copying it via my launch batch file into the text folder. Are you saying that it will have to be manually loaded each time? That's going to be a problem.

--