Page 1 of 1

/varset error

Posted: Sat Apr 03, 2004 12:47 pm
by mcnealis
Im suprised I havent seen this posted.. Maybe its just my computer. What do you think:

/declare test global
/varset test blahblah
/echo @test
[MQ2] blahblah
/varset test 1
/echo @test
[MQ2] 1est
/varadd test 1
/echo @test
[MQ2] 2.00
/varset test blah
/if "@blah"=="blah" /echo true
Couldn't find a comparision operator in 'blah'

.. I ran the uservarstest.mac and nothing passed. It always adds this mysterious character to every variable

any ideas?
thanks
-Alco

Posted: Sat Apr 03, 2004 1:25 pm
by wassup
Not going to bother with the dumb poll, but it seems there is a problem with variables with the new system Lax is working on. I had the same problem with something I was doing as part of the readme update...

http://macroquest2.com/phpBB2/viewtopic.php?t=6098

Posted: Sat Apr 03, 2004 2:06 pm
by dont_know_at_all

Posted: Sat Apr 03, 2004 2:08 pm
by dok
I tried all the commands you posted and got exactly what I should have. (even with the @blah instead lf @test at the end, but it returned false for that statement with @blah in there. true with @test. I didn't get any of those  characters in mine, or variables being combined like you're showing.

but, I did compile with both the new data system, and the old parm system both active.

Posted: Sat Apr 03, 2004 3:18 pm
by wassup
dok wrote:I tried all the commands you posted and got exactly what I should have. (even with the @blah instead lf @test at the end, but it returned false for that statement with @blah in there. true with @test. I didn't get any of those  characters in mine, or variables being combined like you're showing.

but, I did compile with both the new data system, and the old parm system both active.
That's why. If you disable the old system, that is when the problems appear.

Posted: Sat Apr 03, 2004 3:26 pm
by mcnealis
Works like a charm!! Thanks so much!!!