FrontScripts and backScripts are part of the normal message path and aren't exclusive to any stacks. You might be able get away with private handlers and functions triggered in a frontScript but you have to be extra careful to always pass all standard messages or you'll prevent stuff from working correctly all over the IDE.
Scripts in behaviors are limited to the objects they are assigned to, so would seem to be a better option. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design > On Nov 21, 2015, at 6:10 PM, Dr. Hawkins <doch...@gmail.com> wrote: > >> On Sat, Nov 21, 2015 at 5:46 PM, Scott Rossi <sc...@tactilemedia.com> wrote: >> >> 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. > > > Thanks. > > I need to intercept, among others, entry and exit to fields, change of > stack, etc. > > behaviors won't work, as far as I can tell, as each of these stacks also > has its own sizable scripts. > > Would this be a job for back scripts, or maybe chained behaviors? > > > -- > 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
