Thanks for posting, but no i didn't resolve the issue. I attempted several different process concepts, utilizing different files for both the main and enterprise CUI's to see which way would be the best to deliver tools and workspaces to a large workgroup. In then end I havn't been able to accomplish what I set out to do:
My concept was this:
1. Utilize the Enterprises CUI to deliver our custom tools, modified standard ACAD tolls, modified contextual tool states AND company standard customized workspaces.
2. Concolidate the ACAD Mechanical and core ACAD cui files in order to take advantage of tools from both
2. Utilize the Main CUI to allow users to save their personal workspaces and to deliver the core ACAD tools.
What I found:
1. Workspaces in the Enterprise CUI won't work due to the quick-access toolbars. When loading a workspace from the Enterpise CUI I would contantly get a warning that it was "read only" and couldn't create the quick access toolbar (this is when ACAD is loading the interface, this is not me working through the CUI editor trying to update a read-only file). This would happen even after I would deisgn the toolbar within the CUI implicitly and assign it to the workspace.
a. Most frustratingly, the quick access toolbar would somtimes appear within workspaces that they weren't associated with. I would then get the same error because ACAD was attemtping to write some CUI information to my read-only Enterprise file.
2. I couldn't use the Enterprise CUI to deliver core ACAD tools (in modified form) without having to recreate any associate icons. Even when "importing" from another CUI, the core commands are frustratingly locked out from us to be able to modify and therefor deliver in ways specific to our organization. Unless the ACAD cui and associated DLL files are coordinated properly I would end up with the "?" icon. I had wanted to deliver, company wide, modifications to ribbon states and other contextual tool states from a central file. However this became troublesome enough that I've abandoned the idea.
These were just a coupld of the issues I encountered. In the end I wasn't able to accomplish what I thought would be an efficient way to manage company standards from a single location.
I'm no CUI expert, but not a newby either. I worked through quite a few work-flow possibilites and ran into quirky results at most turns. At this point i'm of the impression that Autodesk doesn't have it's work-flow thoughts quite squared away on the use of these files.
