Using return in a command script

[Mike Kerner]

This is for testing and debugging it, Bob.  I'm not proposing that you
leave it as a global.

On Wed, Oct 26, 2016 at 4:56 PM, Bob Sneidar <bobsneidar at iotecdigital.com>
wrote:

> Globals are fine if you only have one project open at a time. Otherwise
> you have to be careful to name all your globals to be specific to the stack
> which created them.
>
> As I said, I am using properties to store persistent values these days.
> This way I can make portable cards or stacks I can add add to any project,
> and they won't walk on each other's "variables".
>
> Bob S
>
>
> On Oct 26, 2016, at 13:37 , Mike Kerner <MikeKerner at roadrunner.com<mailto:
> MikeKerner at roadrunner.com>> wrote:
>
> just for the heck of it change the variable to a global so you can track it
> inside and out of the handler, and see what happens.
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."