Hi Gregory, Instead of putting an openStack handler in every substack, it is much easier to move the openStack in your main stack from stack level to card level. If the openStack handler is in a card script, it won't be triggered by opening a substack.
-- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage: http://economy-x-talk.com Twitter: http://twitter.com/xtalkprogrammer KvK: 50277553 Send me a friend request on Facebook if you like https://www.facebook.com/marksch On 11 sep 2011, at 17:22, Gregory Lypny wrote: > Hi Mark and Jacqueline, > > The substacks had PreOpenStack handlers that called a library stack and > sometimes emptied out some fields, but what they did not have OpenStack > handlers. The absence of OpenStack handlers appears to have been the problem > because, after the the sub-stack executes its own PreOpenStack, the main > stack, for whatever reason, executes its OpenStack. This, of course, can be > disastrous if the main stack is intended to initialize an app or perhaps > contains sensitive material that should not be revisited! My fix is to > include an OpenStack handler with nothing in it in every sub-stack in order > to trap the message. > > on OpenStack > — Do nothing > end OpenStack > > > Gregory _______________________________________________ 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
