I recently discovered Classic Shell when I needed a start menu for Windows 8,
and I've quickly fallen in love with it and with the ability to add custom
menu items. However, a serious limitation is that when I create a shortcut or
"link" to a file, there is no way to include command line arguments for that
file. They are just ignored, and the only workaround I can find is to create a
link to a batch file that launches the program instead. But that's a lot of
needless work.
This is a serious limitation, because a lot of programs need command line
arguments to run correctly. Are there plans to add this ability?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Maybe it's a good idea to mention this in the tooltip help for "Command:". It
is not clear to new users what to use "Command:" for and what to use "Link:"
for.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Currently the documentation says: custom executable string - this can be a name of a program and its arguments, or even a URL (like http://www.google.com). Environment variables like %SystemRoot% are supported
How can this be any more clear?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I meant in the Tooltip help. It could say this to help the user DECIDE
between Command and Link.
Use the 'Command:' field if you wish to add a custom command with parameters
in your Start Menu. The command determines what the item does when clicked.
Use the 'Link:' field if you wish to add a shortcut to a file or a folder.
Folders open as sub-menus. You can use environment variables. Note: Buttons
with sub-menus cannot have link.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I recently discovered Classic Shell when I needed a start menu for Windows 8,
and I've quickly fallen in love with it and with the ability to add custom
menu items. However, a serious limitation is that when I create a shortcut or
"link" to a file, there is no way to include command line arguments for that
file. They are just ignored, and the only workaround I can find is to create a
link to a batch file that launches the program instead. But that's a lot of
needless work.
This is a serious limitation, because a lot of programs need command line
arguments to run correctly. Are there plans to add this ability?
If you want command line arguments, use the Command setting, not the Link
setting. You will have to provide your own label and icon though.
Maybe it's a good idea to mention this in the tooltip help for "Command:". It
is not clear to new users what to use "Command:" for and what to use "Link:"
for.
Thank you! That solved my problem.
And as xpclient said, it's not clear at all in the documentation.
Currently the documentation says:
custom executable string - this can be a name of a program and its arguments, or even a URL (like http://www.google.com). Environment variables like %SystemRoot% are supported
How can this be any more clear?
I meant in the Tooltip help. It could say this to help the user DECIDE
between Command and Link.
Use the 'Command:' field if you wish to add a custom command with parameters
in your Start Menu. The command determines what the item does when clicked.
Use the 'Link:' field if you wish to add a shortcut to a file or a folder.
Folders open as sub-menus. You can use environment variables. Note: Buttons
with sub-menus cannot have link.