Dynamic variables issue

[TheThingIs]

so I can do this:
Set integer [{TXT:EDDI commodity ejected commodity}] to [{TXT:EDDI commodity ejected commodity}] minus [{INT:EDDI commodity ejected amount}] (save value to profile)

but I can't do this:
Begin Integer Compare : [{TXT:EDDI commodity ejected commodity}] Is Less Than 0

it complains that I can't have colons in the variable name

[Pfeil]

Only the "Text" data type allows token input at the moment.

You can use the "{EXP:}" token to do your evaluation:

Code: [Select]

Begin Text Compare : [{EXP: {INT:{TXT:EDDI commodity ejected commodity}} < 0}] Equals '1'
    Write '[Purple] True' to log
End Condition


[Gary]

I'll take a look at it.  Thanks for the heads-up!

[TheThingIs]

Cheers Gary.

Pfeil, setting an integer with a token works fine, it's the compare which doesn't. Good work around though, thanks for that.

[Pfeil]

setting an integer with a token works fine, it's the compare which doesn't.

I was actually speaking in the context of "Begin X Compare" action, but I can see that could've been phrased better on my part.

[TheThingIs]

someday we must teach Pfeil that there are other commands in VA not just EXP:

:p

[Gary]

EXP covers a multitude of sins

Ok, so I've looked into this.  The reason that the text type works is because since it is text, it is doing a direct compare.  The resolved value of the token is used instead of the value of a variable.  It's a shorthand way of not having to resolve the value of a token ahead of time to do a text compare (saves a step).  Seems kind of out of place, but I recall somebody asking for it (I can't remember half the crap this thing does any more).  It doesn't resolve to a variable name, which is what you are trying to do with it.  You'll need to resolve the variable name ahead of time (sorry!).

[TheThingIs]

That's fine, I can do what I need to do and that's all that matters