When I start MicroStation (CE Upd.13) the recent files will show in the Work Page. In the Work Page there's also a "Browse" button to find another file. When I hit the "Browse" button it will open in the recent used folder (that's controlled and stored by the user preference file).
I some cases I have placed a shortcut to start MicroStation in a specific folder and I would like the "Browse" button to look in that specific folder (using fx $(_WORKDIR)). So I'm seeking a possibility to control in which folder the Browse button will open ...fx a variabel similar to the one when browsing for references: MS_REF_DEFAULTATTACHDIRECTORY. ...it could be MS_DGN_BROWSE_DEFAULTDIRECTORY :-)
In other words: I want to be able to ignore the recent folder stored in the user preference file and use a variable to control the "Browse folder". I know the presences of MS_DEF and _USTN_WORKSETDGNS but as far as I can see they only "works" the first time a new WorkSet is chosen (afterwards the upf takes control).
The reason why I'm askinng is that I want to minimize the number of WorkSets or upf files.
I've always used MS_DEF. Currently for CONNECT I have it set in my workset config. We have a separate workset for each project so I can have it open to the project specific folder. You could set it in the Client config and have it point to one specific client folder rather than project specific folders.
I'm sure there is another way to handle it, but I tend to stick with what works for me and is proven.
Power InRoads v8i V08.11.07.615
Microstation CONNECT U13 10.13.01.01
ORD CONNECT 2019 Release 2 U7 10.07.03.18
Hi mwlongThanks for your reply - unfortunately I can't see that MS_DEF helps controlling the folder (path) in which the Browse button will open (unless it's the first time you open a new WorkSet).
THe more i look into this, I believe MS_DEF is the key variable. Not sure why it is not working for you. Maybe run a debug and see if you can pin down what is happening. You can submit a service request and have a Bentley Tech look at it.
I've tried to run a debug and "investigate" what's happening - but everything looks nice and MS_DEF = $ (_USTN_WORKSETDGNS).I'll try to submit a service request ...my "feelings" tells me that it requires a new variable that overrules the upf history.
Thanks again for your thoughts and suggestions.
Best regards Anders
As far as I can see we would need to make changes. In V8i folder paths listed in the PCF under MS_DEF would be added to the Folder History pop-downs in addition the the 10 entry personal MRU list.
This is still the case for file dialogs in CONNECT Edition that currently continue to use older dialog designs with these file/folder history drop-down menus at the top right. Adding MS_DEF path definitions to the WorkSet.cfg will include them in the MRU list. The new dialogs with the file/folder history drop-down menus above the filename field do not do this.
If you would find this useful please file a service request mentioning Enhancement 1093851.
Answer Verified By: Anders W
Thankyou very much for your reply on this subject. It confirms me that this isn't possible in the current "state" of MicroStation CONNECT. In the meantime I have managed to persuade my client to start MicroStation in another way (adding the WorkSpaces and WorkSets in the HKEY_CLASSES_ROOT\Bentley MicroStation Design\Shell.. Reg.key). Therefore they just needs to double click at the dgn file when they are running their default WorkSpaces/WorkSets.Therefore I wont file a service request ...but I'm happy to hear that you do have plans for "renewing" the old dialogs and the corresponding configuration variables :-)
One thing that I failed to mention is that we use a workspace switch in our Microstation shortcut. When I right-click on my CONNECT icon this is what the target looks like
"C:\Program Files\Bentley\MicroStation CONNECT Edition\MicroStation\microstation.exe" -wr\\engdat1\COMMON2\MSV8i_support\Workspace\standards\
This path is where we have a workspace stored for some legacy projects that we are finishing the drafting tasks using CONNECT. Maybe something like this will solve your issue?