CONNECT -View Fit All key in?

What is the key combination for View Fit All? It's 4,5 in SS3.

  • 2

    Unknown said:
    So what is the best location for to place something that is specific to local hardware. I.E. Setting QV_D3DVERSION = 9 for Direct X driver issues

    Personally I would create a file something like "PCspecificChanges.cfg" and place it in one of the directories (C:\Program Files\Bentley\MicroStation CONNECT Edition\MicroStation\config\system) that process*.cfg. This way you can easily undo the changes that you make and you are not changing a file we deliver.

    In Addition:

    I agree with Phil also. For that specific variable it would be a system variable since it would be needed and used by all versions.

    I think though what David is trying to get at is how and where does he set individual settings for all users of a specific machine.  In that case I would do as I describe above.  There are many ways to skin a cat. It's just which way are you comfortable with and know and can support long term.

    As Liam asked who do you want to see the change.

    User = Personal.cfg
    Users of a machine = System environment variable or if it is application specific the an application MyOrg specific cfg
    All user = Organization Level
    All users of a WorkSpace (and all of its WorkSets) = WorkSpace Level
    All user of just a WorkSet = WorkSet level

    Please note that all the Q3 variables are really for debugging purpose and are not designed or tested to be used as a long term solution.  The long term solution is to upgrade or down grade the video drivers.

    Please note this topic has digressed from the original posters question.  If further discussion is needed please create a new thread.

  • You probably should set that one as a system environment variable.

      

  • Unknown said:
    "who will actually need this variable?"

    Everybody who uses that specific PC.

  • If I'm understanding correctly, surely you could put this variable on any level? Personally, I would put it on the organisation level (standard.cfg) since it seems that the only 'wrong' answer here would be to put it in WorkSpaceSetup.cfg or any config file delivered with CONNECT. The question to ask yourself is "who will actually need this variable?" that would drive your decision regarding what level to define the variable on.
  • So what is the best location for to place something that is specific to local hardware. I.E. Setting QV_D3DVERSION = 9 for Direct X driver issues