Assigned command & parameters passed by command line

[Choubi]

I am executing a macro and passes some of its parameters by command line.
I was wondering if the command "assigned>" works with those transmitted parameters, because it always returns me false.

Code example:

Command line call : "myMacro.exe /rate=9600"


Then in the macro script:

Message>rate
Assigned>rate,isRateAssigned
Message>isRateAssigned

The first message will show "9600", the seconde "FALSE", whatever I do. but the variable obviously is assigned!!
Can someone help me? I couldn't find any post about it...

Thanks a lot,

greetings from Switzerland

[armsys]

Hi Choubi,

Rule Number 1 in Macro Scheduler coding is to kill all trailing spaces relentlessly. Are you sure neither Assigned>rate,isRateAssigned nor Message>isRateAssigned contains trailing space(s)?

Happy scripting.

[Choubi]

Hi armsys,


Have you tried such a code at your place (with a exe file)?

Message>rate
Assigned>rate,isRateAssigned
Message>isRateAssigned

and call : myMacro.exe /rate=9600

I did indeed remove trailing spaces. I checked manually and then used the "edit" "remove trailing space". The problem doesn't come from here. I also tried the %variable% style. I have already done some scripts and read a lot of posts on this forum. Must say thank to you, Bob and the support for the useful information.

I really think I can expect Assigned to return TRUE, or am I expecting too much from Macro Scheduler?

Thanks for the help

Choubi

[armsys]

Hi Choubi,

1. I'm terribly sorry for pointing you to a wrong direction.

2. I would like to confirm that all your reported anomalies can be repeated here.

3. Please allow me to offer a work-around solution:
Message>rate
Let>xrate=rate
Assigned>xRate,isRateAssigned
Message>isRateAssigned

I tested the above script fully without any surprise. That's, the script was compiled per your requirement.

4. Please allow me to postulate: Assisgned> can only "see" local variables. The above-mentioned "rate" wasn't created locally; therefore, Assign> deems it "FALSE". What an unfortunate misunderstanding!

Happy scripting. Hope you enjoy using Macro Scheduler.

[support]

Hi,

I've looked at this and unfortunately it is in fact the case that Assigned is not checking variables passed as parameters. This is an ommission and will be fixed in the next release.

[Choubi]

I would be glad to have the next release for free

Thanks armsys for the hand, but your code is not still what I want, since it will return true, even if rate is not passed as parameter..

I have tried several around. Nothing worked. Perhaps the key is to do so:

Let>xRate=rate

And then some VB script that checks if xRate is a string (rate not Assigned) or an Integer (rate assigned).

Does someone has a better idea? I am not at ease with VB...

/Choubi

[Lumumba]

if xRate is a string (rate not Assigned) or an Integer (rate assigned

I guess MSched lacks similar commands, which in this case are from AutoHotkey.
if var is type
if var is not type

maybe stupid - a value divided with 1 will/should return "0" if not a number

Let>Var=ThisIsAText
Let>VarValidateResult=%Var%/1
If>VarValidateResult=0,NotANumber

[Choubi]

Hej Lumumba,

your code unfortunately doesn't make the trick for me.

Let>Var=rate
Let>VarValidateResult=%Var%/1
If>VarValidateResult=0,NotANumber

If I execute it, VarValidateResult is equal to "rate/1" and not to 0 as you say..

That's too bad! Thanks any way

I hope we will soon be able to end this topic, I am still looking for the solution with pure Macro Scheduler syntax, but I think it's not possible.

[Lumumba]

Let>Var=12345
Let>VarValidateResult=%Var%/1
If>VarValidateResult%Var%,NotANumber

Label>ANumber
MessageModal>This is a number: %Var%
Goto>Done

Label>NotANumber
MessageModal>This is not a number: %Var%

Label>Done

Tested !

[Choubi]

That does the trick

Thanks