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 <mikeker...@roadrunner.com<mailto:mikeker...@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@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
