In CE17 there seems to be another layer of messy configuration options bar in already confusing config jungle. How can I get rid of them? Our Microstaton users no need to access any example configs as we use our company workspace only. Therefore I would like to turn obsolete items off so that only our own config options would be visible. What's the point making the GUI more complicated? Who needs this?
What is the relationship between ConfigurationSetup.cfg (in c:\ProgramData..) and configuration.xml (in User Pref folder) when Microstation launches? Does the XML read the CFG file? I need to know this when deploying out to 250 users.
Hi Bob,I haven't tried this with Update 17, but you could try setting both _USTN_USER_CONFIGURATION and _USTN_CONFIGURATION to your configuration path (as either command line arguments or as Windows Environment Variables) and that should ignore the local and custom configuration setups.
No idea what that thing is for (for someone else), but I'd like to know if I can just make it all go away. I hate having stuff like that up on my screen that I must constantly ignore.
Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley
looks like Bentley's getting ready for an early easter egg hunt.
Well this is cute. There is a new variable:
_USTN_CACHECFG that points at the cache.ucf file. It is locked.
There is also a _USTN_CACHEWSCFG that points at a WORKSPACE.ucf where WORKSPACE is the name of the (current?) workspace, the path is the user prefs folder. This file doesn't exist on my system howerver.
I added a variable to the cache.ucf to see the order it is loaded in and it loads before the Personal.ucf so theoretically anything in the Personal.ucf should override the cache.ucf.
I've no idea why these cache files are needed either.