Beta 7.4 says it added a command line option while compiling. I want to make it so it doesnt have the flashing icon when running. And i looked in the help file, and it said to use msched -NOSYSTRAY ...i put that in where it said include parameters(when going to compile)....and i get ann error like let>msched, = Missing. I am a complete newb with the command line stuff. Any help would be appriciated. Thank you very much.
Mark Gevry
command line?
Moderators: Dorian (MJT support), JRL
Leave out 'msched' when putting command line parameters into the compiler options:
Just add the following:
-NOSYSTRAY
If you were to run Macro Scheduler itself from the command line and wanted to stop it putting the icon into the system tray you would type:
msched -NOSYSTRAY
msched.exe is the name of the Macro Scheduler executable. The command line parameters are what come after the executable.
In the compiler we use the same command line parameters, but we don't insert the executable name as that makes no sense.
Command line parameters you can compile in with the compiler are:
-NOSYSTRAY
-HIDE
-LOGFILE=somelogfile.log
And macro variables, e.g.:
/myvar1=freddy /somevariable2=sally /etc=etc
myvar1 and somevariable2 would be referenced in the macro and would now have the values freddy and sally. Being able to compile in variables like this means you can have more easily customised executables without having to edit the code and can more easily work from one source when compiling multiple versions with customisations.
Just add the following:
-NOSYSTRAY
If you were to run Macro Scheduler itself from the command line and wanted to stop it putting the icon into the system tray you would type:
msched -NOSYSTRAY
msched.exe is the name of the Macro Scheduler executable. The command line parameters are what come after the executable.
In the compiler we use the same command line parameters, but we don't insert the executable name as that makes no sense.
Command line parameters you can compile in with the compiler are:
-NOSYSTRAY
-HIDE
-LOGFILE=somelogfile.log
And macro variables, e.g.:
/myvar1=freddy /somevariable2=sally /etc=etc
myvar1 and somevariable2 would be referenced in the macro and would now have the values freddy and sally. Being able to compile in variables like this means you can have more easily customised executables without having to edit the code and can more easily work from one source when compiling multiple versions with customisations.
MJT Net Support
[email protected]
[email protected]
