Why are you putting the global for the substack inside a handler? globals don't live there. It should be OUTSIDE the handlers in the substack script.
On 9 July 2011 23:02, Slava Paperno <sl...@lexiconbridge.com> wrote: > In openCard script of the main stack: > > global gBgColor > put 0, 0, 0 into gBgColor > > > In a button script in a substack: > > on mouseUp > global gBgColor > > answer color with gBgColor --white is selected > put it into gBgColor > > put gBgColor & cr after msg > --255, 255, 255 > end mouseUp > > In the Variables panel below script editor (after it is refreshed), > gBgColor > is shown to be 0, 0, 0. > > In the Message box: > > put gBgColor > --0, 0, 0 > > > In other words, the change to a global variable that is made in a substack > is not available to the global variable of the same name in a script in the > main stack. > > Just last week I carefully followed the discussion of the use of global > variables (and even participated a little by quoting the User Guide on the > availability of globals to all substacks), but now I see the same problem > that was reported by the original poster. > > Is it just me now? Or is it the late hour? > > Slava > > > > _______________________________________________ > 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 > -- Stephen Barncard San Francisco Ca. USA more about sqb <http://www.google.com/profiles/sbarncar> _______________________________________________ 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
