Model tree .cfg files vs .ui files

[davehaigh]

I noticed in Creo 10 that if I save a model tree configuration showing specific columns etc, that it is saving as a .ui file. It appears to me that this file is saving more than just the columns displayed in the model tree, it's saving all the modifications to the .ui that are present in the current session of Creo. 

I find this a bit disconcerting. I only want to have a file that changes what columns are displayed in the model tree. Which is what the .cfg file did and still does in Creo 10, but there appears to be no way to create a .cfg file in Creo 10. 

We have in our loadpoint a .ui file that all users see. Then in the cache location we have a .ui file that is specific to that division. Both of these are really only to adjust what additional tabs are in the ribbon, but I found out today that they don't just control ribbon, they control all aspects of the Creo UI. 

We have different startup for editing the ribbon, one for the load point ribbon, one for the cache ribbon, and one for the user ribbon. All of these startups load our standard configs with their mapkeys for that environment, but with only one .ui file in the start up directory. That way we or the users are only editing one .ui. That means the .ui seamlessly combine to create the ribbon each group gets with the normal startup for their division. This means we can update the ribbon for a division and it will not affect all users, and since we put these files in the loadpoint and cache with our Creo startup scripts, user get any changes the next time they start up. 

Am I missing something here about .ui files being used for the model tree. We have mapkeys that can change what colums the user wants to show in the model tree, and those mapkeys are in the tab of the ribbon for that division. 

I don't want to load a .ui file for the ribbon that might change other aspects of the UI. 

Thoughts?????

[DB@HuscoInt]

The functionality of the new tree UI files is interesting. I have found them to be a bit tedious and only seem to work best if you want a default tree to be provided for all users in an admin_customization.ui. Importing it though the tree menu doesn't seem to work as intended like an original tree config file. 

As a work around we set the hidden config "allow_tree_config_save" YES to enable the saving of the original tree config files. We store these in a folder that the mapkeys pull from to toggle in-between them which makes it easier when doing certain operations.

Attached is some example tree mapkeys from Econocap Software's CreoLib Demo

[davehaigh]

I was able with your syntax in the mapkey to get it to load my old .cfg files, But I can't figure out how to save out a .cfg file even with that config option. 

What is are the picks I need to make?