What is the key combination for View Fit All? It's 4,5 in SS3.
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?
If its not broke don't try and fix it.
Unknown said: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?
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.
stuartw said:I'm sure that you have previously said as part of the EAP forum that adding configs to this file was OK.?
Where are the Organization/WorkSpace/WorkSet/Role levels.in the standard install?
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?
John Frampton it is recommended that you do not make changes to this file.
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
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.
Unknown said:"who will actually need this variable?"
Everybody who uses that specific PC.
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.cfgUsers of a machine = System environment variable or if it is application specific the an application MyOrg specific cfgAll user = Organization LevelAll users of a WorkSpace (and all of its WorkSets) = WorkSpace LevelAll 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.