When I attempt to use No Workspace (Client) -> No Workset Browse uses the previous Workspace name to look for a folder No Workset\DGN.
This results in an error and does not allow browsing for files using No Workspace -> No Workset
@DavidG - But can you tell me what controls the location of the No Workspace option (see below). Is there a cfg file that this calls up? - there is no configuration to control this.
Tim Hickman said:But can you tell me what controls the location of the No Workspace option
Can I tell you? I have no idea. I still don't understand why something that suppose to do nothing requires a location and a workset, let alone how or what you are internally searching for to determine the proper location of nothing.
I point workspaces to look on my server where I have my project workspaces and those workspace configs point to locations where I keep my project worksets.
Take a look at (but DON'T change) msconfig.cfg, try a search in the text for "nowork" just to find the right area...
Lines 301 to 306 define the place where NoWorkSpace/NoWorkSet.cfg lives.
In my test setup with drives P (= project data: WorkSpaces/Worksets) and W (= resources: Organization) I can reproduce the information message (note this is not an error message, it speaks the truth, MicroStation is looking for a file and it is not there!) by deleting the copy of NoWorkSpace/NoWorkSet.cfg I put there as described in Solution 1 below.
I offer two solutions:
The easiest: Copy NoWorkSpace/NoWorkSet.cfg to the place it's looking.
No one likes untidy folders so in C:\ProgramData\Bentley\CONNECT Edition\Configuration\WorkSpaceSetup.cfg which is where I assume redirection to your equivalents of P and W is being done add a variation of the if loop contained in msconfig.cfg, change the two instances of the variable _USTN_WORKSPACESROOT to _USTN_ORGANIZATION where indicated:
In my case this is:
# To hide the NoWorkSpace folder from the users
%if !defined (_USTN_WORKSETCFG) && exists ($(_USTN_ORGANIZATION)NoWorkSpace/NoWorkSet.cfg)
_USTN_WORKSETCFG = $(_USTN_ORGANIZATION)NoWorkSpace/NoWorkSet.cfg
_USTN_HAVEWORKSET = 0
_USTN_HAVEWORKSET = 1
Where I have already defined:
_USTN_ORGANIZATION = W:\MstnCONNECT\Organization\
Copy NoWorkSpace/NoWorkSet.cfg to the matching location
This can be anywhere you like (on your LAN!) as long as the location and the if statement match. You could change the folder name but if it is out of sight why bother, that will only obscure its purpose.
Answer Verified By: DavidG
Marc Thomas said: but if it is out of sight why bother, that will only obscure its purpose.
What is obscure it why the file needs to exist at all. Is its sole purpose appears to be so we don't get an error message?
So far we've just gone in circles. It needs to exist because the program is looking for it. Is that its whole reason for existence?
Marc Thomas said:If it is likely to be a common choice, why so?
Marc Thomas said:MicroStation has always been designed to use project configurations
why shouldn't there be an invisible way to do without, to just fire up and get on - in a single user environment for example?
As long as this tiny configuration file is in the expected place (or configured to be hidden away, if the presence of the 'NoWorkSpace' folder is unacceptable) the informative message will never be seen, so yes you can just fire it up and get on with it. If you don't want to engage with the Workset features that's fine.
Looking again at the content of C:\ProgramData\Bentley\CONNECT Edition\Configuration\WorkSpaces\NoWorkSpace\NoWorkSet.cfg it says at the top:
# Configuration File used for opening stand-alone DGN files that don't
# belong to a WorkSet.
# Set search paths to 'My Documents'
That is what this file is designed to do.
Why is it using 'My Documents'? Because that folder is always present so we know it will be found. We deliver a working testable configuration that is then amenable to change.
For anyone that does not want the search paths for No Workset to point to 'My Documents', the usefulness of the NoWorkSet.cfg file turns out to be that the network/standalone/'NAS box' copy of NoWorkSet.cfg can be edited to point to the desired location, e.g:
%if exists (C:/MySketches/) _USTN_WORKSETROOT = C:/MySketches/%else _USTN_WORKSETROOT = $(HOMEDRIVE)$(HOMEPATH)/%endif
So quite handy really.
Marc Thomas said:MicroStation has always been designed to use project configurations. Open V8i without a PCF and you might well get errors depending on the configuration, generally in a text window.
Yes but a PCF actually does something. Sets up various paths, etc to expedite certain processes. Simply opening a file generally does not require a specific configuration. Files that are dependent on external factor (configurations) are problematic. Especially if shared between companies.
Marc Thomas said:This message is an informative one to tell you that the configuration file that has been designed to handle a user's choice to select No WorkSpace/No Workset is not in the location that it is expecting to find it
Find what? A file that doesn't do anything. It only needs to be there because the program is to dumb to know it doesn't need a .cfg file when the user specifies "no workspace" (i.e. specialized configuration).
Marc Thomas said:There are two solutions available at present, as described above
These are solutions to prevent a error dialog box from popping up. Again were going in circles.
Marc Thomas said:The way this works may well be due for refinement
Marc Thomas said:Is choosing No WorkSpace/No Workset likely to be a common user choice or is it just that this came up during testing?
No, I'm working in a real working environment. Well sort of. I still need to go back to SS3 to perform basic tasks that Connect fails at.