Shortcut1Link="firefox.exe"
Shortcut1Text="Firefox"
Shortcut2Link="C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\devenv.exe"
Shortcut2Text="Visual Studio 2019"
Shortcut3Link="C:\ProgramData\Microsoft VS Code\Code.exe"
Shortcut3Text="VS Code"
Now, Firefox works flawless. Visual Studio 2019 does (apparently) nothing and vs code opens the ProgramData folder, which lead me to try doubling the backslash (nothing changed) and after backslashing my spaces (also not working).
Shortcut1Link="firefox.exe"
Shortcut1Text="Firefox"
Shortcut2Link="C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\devenv.exe"
Shortcut2Text="Visual Studio 2019"
Shortcut3Link="C:\ProgramData\Microsoft VS Code\Code.exe"
Shortcut3Text="VS Code"
Now, Firefox works flawless. Visual Studio 2019 does (apparently) nothing and vs code opens the ProgramData folder, which lead me to try doubling the backslash (nothing changed) and after backslashing my spaces (also not working).
Even if not absolutely required and not even needed, for me seems a good practice to get used to use quotations when posting measure / meter names as well. For instance instead of [!ToggleMeterGroup SpyMissionMenu] I'm always using [!ToggleMeterGroup "SpyMissionMenu"].
Again the bang written with no quotations works same way. It's just a matter of habit.
balala wrote: ↑July 28th, 2019, 5:13 pm
Even if not absolutely required and not even needed, for me seems a good practice to get used to use quotations when posting measure / meter names as well. For instance instead of [!ToggleMeterGroup SpyMissionMenu] I'm always using [!ToggleMeterGroup "SpyMissionMenu"].
Again the bang written with no quotations works same way. It's just a matter of habit.
I'm not sure I entirely agree with this. I think a better habit to get into is to never use spaces in measure or meter names.
jsmorley wrote: ↑July 28th, 2019, 9:15 pm
I'm not sure I entirely agree with this. I think a better habit to get into is to never use spaces in measure or meter names.
Definitely. Not using spaces nor into measure, nor into meter names is definitely the best practice, but even if in the names are no spaces, including the names into quotations is still a good practice in my opinion, same as we add quotations to the number in a [!SetVariable MyVariable "0"] bang. The quotations are not needed nor here, but recommended to be used.
balala wrote: ↑July 29th, 2019, 9:38 am
Definitely. Not using spaces nor into measure, nor into meter names is definitely the best practice, but even if in the names are no spaces, including the names into quotations is still a good practice in my opinion, same as we add quotations to the number in a [!SetVariable MyVariable "0"] bang. The quotations are not needed nor here, but recommended to be used.
There is no right or wrong approach for this really. I just make it a firm practice to never use spaces in any [SectionName] or Variable name, and since the static names of options never have spaces, I really only have to remember to quote any "values" I use in a bang. I don't quote section names or variable names or option names. This actually visually helps me see what is what in the bang.
Having said that, you were entirely correct before. [!ToggleMeterGroup "SpyMissionMenu"] follows this rule, as SpyMissionMenu is a "value" and should really be quoted for consistency of approach.
jsmorley wrote: ↑July 29th, 2019, 10:53 am
There is no right or wrong approach for this really. I just make it a firm practice to never use spaces in any [SectionName] or Variable name, and since the static names of options never have spaces, I really only have to remember to quote any "values" I use in a bang. I don't quote section names or variable names or option names. This actually visually helps me see what is what in the bang.
Having said that, you were entirely correct before. [!ToggleMeterGroup "SpyMissionMenu"] follows this rule, as SpyMissionMenu is a "value" and should really be quoted for consistency of approach.