MS15 Inconsistent use of True TRUE False FALSE

[user5274]

Because not all MS15 commands return a consistent TRUE/True or FALSE/False, is it safe to use a catch-all {TRUE}/{FALSE} to test for returns to MS15 commands?

For example, this command
WaitPixelColor returns TRUE or FALSE

while this command
IsConnectedToInternet returns True or False

So I don't have to remember when to use either is it safe to use:

Code: Select all

If>WPC_RESULT={TRUE}

or

Code: Select all

If>ISCONNECTED={FALSE}

throughout my code, or will i take a performance hit by forcing it into complex mode?

[Marcus Tettmar]

Will make a note of that. Should really be consistent.

These are actually strings as far as MacroScript is concerned so safest thing would be:

If>{Upper(%WPC_RESULT%)="TRUE"}

[user5274]

Great thank you!

I personally know now which commands return what, I just had a partner that decided to "clean up" the code and changed all the "booleans" to uppercase and thats when IsConnected (and another command) broke, drove me crazy for the better part of the day.