Why does MS23 default to Example Workspace/Workset on start up when I don't use these?
With U17 and all previous versions it would default to the last used workspace/workset which in our case is No Workspace/Workset.
I now to click No Workspace/Workset each time to get to the Recent Files list.
RobertArnold said:Check MS_CONFIGURATIONOPTS -- Mine is blank (null).
So is mine but strangely it shows the Level as User. I'm pretty sure that I have not changed this.
Check MS_CONFIGURATIONOPTS -- Mine is blank (null).
When I first installed Microstation 2023, I would not get my recents list. Mstn was not selecting the configuration properly. Once I edited the .xml file from my July 6 posting, Mstn worked o.k. again.
--Robert
This is what I see. Recent Files list removed. Notice I don't have Manage Configuration option.
RobertArnold said:In Microstation CE Update 17, the configuration.xml file came into play to get the list to appear correctly and to get the defaults to work properly.
What list and what defaults?
This is my configuration, which works well...
In Microstation CE Update 17, the configuration.xml file came into play to get the list to appear correctly and to get the defaults to work properly.
Marc,
Thanks for your response but things have moved on since I posted this. I have had to set _USTN_USER_CONFIGURATION in my configurationsetup.cfg because _USTN_CUSTOM_CONFIGURATION is not working as it does with the CONNECT version. I posted this on another thread and am speaking to Support about about why _USTN_CUSTOM_CONFIGURATION and my customised 'standards.cfg' are not being processed. As part of this I now do see the Examples Workspace/Workset when staring MS2023. I also don't have a Manage Configuration Utility.
Marc Thomas said: have not investigated how operating only with No WorkSpace/No WorkSet can be set up in MicroStation 2023 because it is not an appropriate approach and just makes configuration more difficult than it needs to be
Noted but why isn't it an appropriate approach. We don't use Workspaces/Worksets as they don't fit our workflow, but No Workspace/Workset does. Wed are not going to start using Workspaces/Worksets now, after all this time.
Marc Thomas said:In MicroStation 2023 you can set a new variable to point to a folder containing a shared configuration.xml that in a single WorkSet scenario need only contain one configuration. e.g. : MS_CONFIGURATIONXML_PATH = D:/_CONFIG_XML/ A configuration can be set up that uses the WorkSpace/WorkSet to store configuration and points to a data storage location without impacting the data structure, this could be relevant to your situation.
In MicroStation 2023 you can set a new variable to point to a folder containing a shared configuration.xml that in a single WorkSet scenario need only contain one configuration. e.g. :
MS_CONFIGURATIONXML_PATH = D:/_CONFIG_XML/
A configuration can be set up that uses the WorkSpace/WorkSet to store configuration and points to a data storage location without impacting the data structure, this could be relevant to your situation.
I have read what you have written but don't understand what you are saying. What is configuratuion.xml as pretty sure that we don't use it.
All we need to know is that our custom configuration & 'standards.cfg' are being used. Works fine with U17 so why not in 2023?