CONNECT -View Fit All key in?

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

Parents
  • The "4,5" key combination in SS3 works as it does because:
    * Position Mapping is on
    * The Main zone is assigned 12345 etc. by default in the Position Mapping preferences
    * The Position Mapping popup menu mnemonic characters are 12345 etc. (hard-coded in SS3)
    4 pops open the View tools from Main (4th position), and 5 is associated with Fit View in the popup menu because it's in the 5th position.

    CONNECT Edition offers a lot of flexibility in the area of key combinations. Position Mapping is off by default, and Keyboard Shortcuts handle key combinations in this case. The F7 key shows you all the top-level Keyboard Shortcuts in a menu. You can also open the Keyboard Shortcuts dialog to see them all and to modify any key assignment.

    The default key combination for Fit View is Q,L,V. That key combination works as it does because:
    * Position Mapping is off and Keyboard Shortcuts are used
    * Q opens a popup-menu containing lots of tools and submenus
    * L opens the View Tools ribbon group popup
    * V is the ribbon keytip for Fit View

    When any ribbon group popup is open, you can press the Alt key to learn the keytips. You can also show those automatically by turning on the "Show Popup Keytip Hints" option in the Ribbon preferences.

    If you want the "4,5" key combination to work the same in CONNECT as in SS3:
    * Turn on Position Mapping in the Preferences dialog (Keyboard Shortcuts will only be used for those keys not used in PM, such as the Space key)
    * Pin the Main group to all workflows. To do that, access the Main group in the "Task Navigation" workflow then right-click on it to open a menu with "Pin/Unpin Group" options.

    If you'd rather use Position Mapping with the legacy Task Navigation dialog rather than the ribbon, you can define the config var MS_TASKNAVIGATION_CONFIGURATION=1 and switch Task Navigation to one of the legacy presentations in the Preferences dialog.

    You can also change the Position Mapping characters in the Preferences dialog. That includes the characters used in popup menus, which is a new feature in CONNECT Edition.

    For more information on the Position Mapping and Task Navigation options in CONNECT Edition, see communities.bentley.com/.../106051



  • Unknown said:
    T

    If you'd rather use Position Mapping with the legacy Task Navigation dialog rather than the ribbon, you can define the config var MS_TASKNAVIGATION_CONFIGURATION=1 and switch Task Navigation to one of the legacy presentations in the Preferences dialog.

    Just to clarify then, using this config MS_TASKNAVIGATION_CONFIGURATION=1 will remove the ribbon and gives us back the tasks dialog. Is that correct?

  • Surely if you follow what it says, you should be good to go? Extract from WorkSpaceSetup below:
    # WorkSpaceSetup.cfg - Configures WorkSpace for Your Organization
    #
    # The main function of this configuration file is to set the label that
    # your organization wants to use for WorkSpaces. WorkSpaces are the
    # grouping mechanism for WorkSets. The label for this level of grouping
    # could be Client, Facility, Department, Owner, or whatever you would
    # like it to be. The default label is the neutral "WorkSpace". Uncomment
    # the definition below, and set it to your preferred label.

    # A second possible use for this configuration file is to redirect the
    # root directory where your Organization-wide standards are stored to somewhere
    # other than the default. The default is $(_USTN_CONFIGURATION)Organization/.
    # It can be changed by redefining _USTN_ORGANIZATION. The following is an example
    # of how to set it up on a network.

    # A third possible use for this configuration file is to redirect the
    # root directory where your WorkSpaces are stored to somewhere other
    # than the default. The default is $(_USTN_CONFIGURATION)WorkSpaces/.
    # It can be changed by redefining _USTN_WORKSPACESROOT. The following is an example
    # of how to set it up on a network.
  • Please read the thread, my response was in regards to the Variable that David T. recommended setting.

    Unknown said:
    <<SNIP>>When you use MS_TASKNAVIGATION_CONFIGURATION it will give you an additional section in preferences:<<SNIP>>

    stuartw said:
    <<SNIP>>BTW I've set this config in my WorkSpaceSetup.cfg file. Is that correct.

    Unknown said:
    <<SNIP>>Though setting any configuration variable in any cfg file that is read will work it is recommended that you do not make changes to this file. This type of change should be stored in the Organization/WorkSpace/WorkSet/Role levels.


    Regarding.
    stuartw said:
    I'm sure that you have previously said as part of the EAP forum that adding configs to this file was OK.?
    I am almost positive I did not state that adding any random variable to this file is ok. If you can find the post where I did I we correct my statement.
    Where are the Organization/WorkSpace/WorkSet/Role levels.in the standard install?

    Please read the Help documentation, it outlines where these are by default.

  • Unknown said:
    If its not broke don't try and fix it.
    John Frampton
    it is recommended that you do not make changes to this file.

    Seriously?  Whats the point of having it under ProgramData rather than Program Files..../config it its not meant to be modified?

    I am not sure what the point of your post is? If what isn't broke? Please read the file with regards to what type of changes should be made in that file.  The file is there and it can be edited by the end use, though with the recent changes made to the Installer there is no reason for the user to edit this file manually.  The file is not to hold random variables that are mentioned and I was responding to.

  • Unknown said:
    Did John not mean "Organization OR WorkSpace OR WorkSet OR Role levels"? I've currently got mine set at the Organization level

    Yes this is correct.

    Unknown said:
    Surely if you follow what it says, you should be good to go? Extract from WorkSpaceSetup below:

    You are correct that is the intent of the fie.  With the changes we made to the installer from EAP to CR there is no reason for the end user to manually end this file. There is especially no reason to store a random variable that does not pertain to the intent of the file to be stored in it.

  • 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
Reply Children
  • 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.
  • Unknown said:
    "who will actually need this variable?"

    Everybody who uses that specific PC.

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

      

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