Assigned or Not Assigned, That's the Question

Technical support and scripting issues

Moderators: JRL, Dorian (MJT support)

Post Reply
armsys
Automation Wizard
Posts: 1108
Joined: Wed Dec 04, 2002 10:28 am
Location: Hong Kong

Assigned or Not Assigned, That's the Question

Post by armsys » Wed Feb 02, 2011 1:23 pm

In the following code, Assigned> fails to tell the truth: whether the variable has been assigned:

Code: Select all

Let>i=1
Let>j=1
Assinged>Item%i%_%j%,x
Let>Item%i%_%j%=XXX
Assinged>Item%i%_%j%,y

User avatar
Marcus Tettmar
Site Admin
Posts: 7395
Joined: Thu Sep 19, 2002 3:00 pm
Location: Dorset, UK
Contact:

Post by Marcus Tettmar » Wed Feb 02, 2011 2:42 pm

Assigned doesn't work with complex-embedded/array-type variables. Just simple ones. Sorry.
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar

Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?

Jerry Thomas
Macro Veteran
Posts: 267
Joined: Mon Sep 27, 2010 8:57 pm
Location: Seattle, WA

Post by Jerry Thomas » Wed Feb 02, 2011 2:43 pm

Check spelling
Assigned rather than Assinged

What are you trying to do?
Thanks,
Jerry

[email protected]

armsys
Automation Wizard
Posts: 1108
Joined: Wed Dec 04, 2002 10:28 am
Location: Hong Kong

Post by armsys » Wed Feb 02, 2011 4:30 pm

Marcus,
All I need is your confirmation so that I can stop torturing my brain. Of course, there're always alternatives to vet if a complex/array-type variable is assigned with a value. Of course, it would be nice if Assigned> command can support complex/array-type variables in the future releases.
Is it important? Definitely. We don't always know the exact number of array elements. And we don't always know if an array element has been assigned with a value.
Thanks.

armsys
Automation Wizard
Posts: 1108
Joined: Wed Dec 04, 2002 10:28 am
Location: Hong Kong

Post by armsys » Wed Feb 02, 2011 4:38 pm

Jerry,
That's the same question I wish to ask. Yes, it was a misspelling. Probably I drowsed off while typing the command. Amazingly, the MS Debugger didn't complain. Even with "Assigned>," the results are the same. Thanks for pointing out my typo.

Post Reply
cron
Sign up to our newsletter for free automation tips, tricks & discounts