> On Jun 26, 2018, at 13:30 , J. Landman Gay via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Every instance of a behavior maintains its own separate variable values. This > is a feature. Globals are the solution if you want them to share the values. > I don't want to share the variables. I want them to be local to the script. The trouble is, they reset as soon as the handler exits. Inside the handler, they all seem to be fine! And ONLY the openStack handler seems to be having the issue, because any other handler, even preOpenStack will retain the script local values! GAH! Bob S _______________________________________________ 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
Re: Behaviors not honoring script local variables??
Bob Sneidar via use-livecode Tue, 26 Jun 2018 13:42:59 -0700
- Behaviors not honoring script local variab... Bob Sneidar via use-livecode
- Re: Behaviors not honoring script loc... Bob Sneidar via use-livecode
- Re: Behaviors not honoring script... J. Landman Gay via use-livecode
- Re: Behaviors not honoring sc... Bob Sneidar via use-livecode
- Re: Behaviors not honorin... Tom Glod via use-livecode
- Re: Behaviors not ho... Bob Sneidar via use-livecode
- Re: Behaviors no... Bob Sneidar via use-livecode
- Re: Behavior... Tom Glod via use-livecode
- Re: Behavior... Bob Sneidar via use-livecode
- Re: Behaviors not honoring sc... Tom Glod via use-livecode
- Re: Behaviors not honoring script loc... Dick Kriesel via use-livecode
- Re: Behaviors not honoring script... Bob Sneidar via use-livecode
- Re: Behaviors not honoring sc... Bob Sneidar via use-livecode