Could "DEFINE integer VARIABLE | %<x>%::=<value>"be created?

[WWO]

Could "DEFINE integer VARIABLE | %<var>::=<value>" be created please?
[The '=' is the 'new' part.]

It took me a while to figure out why:

6 | RUN ACTION | DEFINE integer VARIABLE | %XX%::-424


was behaving strangely.

'Define' isn't. More like "evaluate and assign".


www.turnssoft.com/conditions.html#integer_variable notes "Equal to (=)"

Could the same syntax be applied here / to assignment, please.

[Steve]

Hmm yeah I see your point. I'll have a look at the code and get back to you. If it's easy to implement I'll consider it for the current update.

At the moment the following results in RESULT being the value of 2:
1 | RUN ACTION | DEFINE INTEGER VARIABLE | %RESULT%::5
2 | RUN ACTION | DEFINE INTEGER VARIABLE | %RESULT%::-3
3 | RUN ACTION | MESSAGE PROMPT | %RESULT%
The initial deceleration at line 1 sets the variable at 5 and every assignment after calculates off the original assignment.

[Steve]

Hi WWO

I had a quick look and it was about a 5 min code addition to get it in.
Its made it's way to the next update. Thanks for the suggestion

minimousemacro.proboards.com/thread/380/update-coming-next-mouse-macro

[cyberchipz]

I agree with Zeak, sometimes I miss updates... meaning, coming here and reading teaches me something new each time! :-) Adding that ::= is a stroke of genius... I can now go and remove all the first lines I wrote to take care of this the old way.. ;-)
I can see that was an easy update! 


2 | RUN ACTION | DEFINE INTEGER VARIABLE | %RESULT%::0
3 | RUN ACTION | DEFINE INTEGER VARIABLE | %RESULT%::-3


2 | RUN ACTION | DEFINE INTEGER VARIABLE | %RESULT%::=-3  
That's what's nice, using 8.3.2.1 for a bit... and it has all of these updates... 
I like this much better. :-) Thanks Steve for all your hard work keeping this APP Alive!!!

Chip