No Workspace/No Workset uses last workspace name and won't allow browsing

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

Parents
  • I am not able to reproduce this issue.
    I redirected my configuration so its a custom location, select a workspace and workset - there is no "recents"listed as this is a clean start. I select the browse button and browse to a file in that workset and open it. I close the file and select no workspace and no workset (again no recents listed) I select the browse button and it allows me to browse and select a file. No error message. I closed MicroStation completely, and restarted it, then selected no workspace - no workset, and still no error.

    Timothy Hickman

    CADD Manager | CADD Department

    timothy.hickman@colliersengineering.com

    Main: 877 627 3772| 

    1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691

  • Tim,

    Do you have a folders setup for No Workspace and No Workset ?
  • 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

    Answer Verified By: DavidG 

  • Unknown 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.

    Unknown 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).

    Unknown 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.

    Unknown said:
    The way this works may well be due for refinement

     My personal opinion is it works this way because somebody came up with lazy workaround to the problem.  Just create a Workspace/Workset call it NoWorkspace/NoWorkset.

    Unknown 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.

    Unknown said:
    If it is likely to be a common choice, why so?

     Yes, if your sharing files you don't want everything getting stamped with site specific data.  There are advantage to having files know what project they belong to but that workset dialog popping up every other time I open a file is getting pretty damn annoying.

  • Marc,

    I appreciate the fact you responded and posted a solution to the error message. I will mark that as the verified answer. It does answer my original post.

    I don't want to drag this out. We just have a fundament disagreement whether such a configuration file should be required.  
    Edit: Or more specifically that users should have to be configuring this when they set up their own workspaces.


    All the best.
    DavidG

  • Marc,

    So I set up MS using this method of pointing to a workset.cfg.  It seemed to be working and eliminates the error message when browsing however I have a cell library that was inadvertently associated with a project.  I now see this when opening the file from "NoWorkspace/NoWorkset.

    How do you unassociated a file from a Workspace/Workset? 

  • I searched MicroStation CONNECT help for "Workset". The second result down, "Including Files in the Active WorkSet" also tells us how to disassociate with a key-in, scroll down to the end of the page.

    Marc

Reply Children