Handlers in libraries are available to all open stacks. If you're relying on standard messages in your library (ie openStack, closeStack, etc) these will get triggered by any stack that opens or closes. You either need to use custom handler names that are only triggered by stacks that "know" the handlers, or you can use behaviors, since these are local to the controls/cards/stacks they're assigned to.
Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design > On Nov 21, 2015, at 5:27 PM, Dr. Hawkins <doch...@gmail.com> wrote: > >> On Sat, Nov 21, 2015 at 4:29 PM, Dr. Hawkins <doch...@gmail.com> wrote: >> >> >> I hacked around it with > > Ugh. It's worse than I thought. > > I've added the hack to closeField and exitField. > > Now it seems suspendStack, resumeStack and the like are all up for this, > too. And then there would be resizeStack, and pretty much every other > basic message I might want to handle. > > All I want is for my (huge) script to act like it was in the mainstack for > my other stacks, which are now mainstacks in their own right, and to keep > the IDE's bloody hands off of it. > > > -- > Dr. Richard E. Hawkins, Esq. > (702) 508-8462 > _______________________________________________ > 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 _______________________________________________ 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
