CONNECT -View Fit All key in?

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

  • 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