If you move the preOpenStack handler to the script of the first card of the mainstack, the substack won't trigger the handler. This is a common method of handling "housekeeping" and other routines that you want run at startup, but don't want triggered by substacks.
Regards, Scott Rossi Creative Director Tactile Media, UX Design On Dec 7, 2010, at 6:19 PM, Glen Bojsza <gboj...@gmail.com> wrote: > Maybe it's me or should this not be happening. Livecode 4.5.1. > > I have a mainstack that has a preOpenStack that does some house keeping... > > I just added a substack that is opened from the mainstack by a user clicking > a button. > > **There is NO preOpenStack in the substack > > When the substack opens the preOpenStack of the mainstack tries to run which > generates an error since none of the objects on the mainstack are on the > substack. > > Should preOpenStack only work with the stack that contains it? > > If this is the proper way the system works then what is the work around? > > thanks, > > Glen > _______________________________________________ > 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
