Thanks, Marcus. Until SK_IGNORECAPS is fixed, I'm using the workaround below. Instead of: Let>SK_IGNORECAPS=1 Send>123./Hello World! use: // Turn off Caps Lock explicitly LibFunc>User32,GetKeyState,CAP_STATE,20 CapsOff Send>123./Hello World! Label>END_OF_SCRIPT // Return to original states If>{%CAP_...

I'm running MS Version 12.0.2 on Windows 7 x64 Ultimate. I don't think SK_IGNORECAPS is doing what's it's supposed to: Let>SK_IGNORECAPS=1 Send>123./Hello World! With the keyboard's Caps Lock key OFF: 123./Hello World! With the keyboard's Caps Lock key ON: !@#>?Hello World1 This should be exactly th...

Your are right, JRL. My script doesn't work as I intended. As you pointed out, it seems that VAREXPLICIT is a write only variable. It always returns 0 regardless of its true value, which you can set with LET> My original snippet was meant to be as side-effect free as possible, by trying to remember ...

I code with VAREXPLICIT=1 in hopes of keeping things clearer with respect to variable expansion in MacroScheduler. This approach seems to be going well, until I needed to access an array element. I couldn't find a way to do so while VAREXPLICIT=1, so had to set VAREXPLICIT=0, assign the array elemen...

mtettmar wrote:You need to compile with the console compiler instead:

msrt_console.exe -COMPILE %SRC% %EXE%

So that's what that msrt_console.exe file was for.

Thank you very much, Marcus.

I'm running Macro Scheduler Pro 12.0.2 on Windows 7 x64. This is the script to be compiled to console app: // COMPILE_OPTS|C:\Users\Khoa\Desktop\x\x.exe||CONSOLE=1|INCLUDES=1| //Set IGNORESPACES to 1 to force script interpreter to ignore spaces. //If using IGNORESPACES quote strings in {" ... "} //L...

If the variable HAS a value and that value is the test text, then a false negative will be detected. In other words, the sample subroutine will fail if the variable TIMEOUT has been set to the text "TIMEOUT". e.g. Let>TIMEOUT=TIMEOUT Understood. I think this is acceptable until this Assigned workar...

Beautiful! Thank you, JRL. Here's the SRT call and declaration packaged up nicely. // This sequence sets the variable TIMEOUT to 0 if it's not already set Assigned>TIMEOUT,result If>{%result%="FALSE"} Let>TIMEOUT=0 EndIf // This call does the same thing as above with SRT SetIfNotDefined GoSub>SetIfN...

To effect an externally initiated compile with the file to be compiled opened in the Script Editor, I ended up create an Macro Scheduler file called qcompile.exe created from qcompile.exe as follows: // COMPILE_OPTS|C:\Users\Khoa\Desktop\InterfaceED Work\InterfaceED\qcompile.exe||CONSOLE=1|INCLUDES=...

Please add my vote for jpuziano's suggestion to allow Assign to test complex expressions. This ability would allow the test and set of a variable if not already defined, to be placed in an SRT for clean application. I've just posted more information on this SRT issue at: http://www.mjtnet.com/usergr...

Hi all, I'm starting to get into Macro Scheduler programming, so I'm not quite sure what's possible and not. I'm finding that I need to check if a variable is defined, and set it to default value if undefined. For example, test the TIMEOUT variable as such: Assigned>TIMEOUT,result If>{%result%="FALS...

Thank you for the quick and informative response, Marcus. I can understand the need to lock script files for data integrity in a networked/multi-user environment. Is there any way you can reduce the scope of the lock? Perhaps a read lock, rather than an exclusive lock? Or if an exclusive lock is nec...

I'm using the latest Macro Scheduler 12.0.2 Script Editor to write a console app on Windows 7 x64. While I have the script file opened in the Script Editor, I can "Save" changes, then "Create Exe" to compile and all is well. However, if instead of using the Script Editor's "Create Exe" function, I r...