Best Practice: Prevent Substacks from Triggering Main Stack Scripts
m.schonewille at economy-x-talk.com
Fri Feb 6 10:12:39 CET 2015
It isn't obligatory to use substacks. You could use two mainstacks
simultaneously. Just make sure to include the additional mainstacks as
files when you build a standalone.
With two mainstacks, the scripts in one stack won't be triggered by
messages from the other. If you have handlers that you want to use in
both stacks, you can put those handlers into another separate stack and
use that as a library with the start using command or by defining front
and back scripts.
Economy-x-Talk Consulting and Software Engineering
Installer Maker for LiveCode:
Buy my new book "Programming LiveCode for the Real Beginner"
LiveCode on Facebook:
On 2/6/2015 07:49, Brahmanathaswami wrote:
> If you put any preopenstack, resizestack, close stack etc. script in the
> mainstack script.. these will be triggered by the same action in a
> What is the best way to avoid this?
> I just moved all those to the main background group of the main stack,
> but I'm not happy with that architecture. I'm so
> use to running most script in the main stack script for simplicity sake
> and ease of finding things.
> I suppose one can install "dummy" handlers in the substacks to match.
> on preopenstack
> end preopenstack
> and since you are not passing anything, I suspect it will prevent
> triggering that handler in the main stack..
> But, what are you veterans doing to handle this?
> Swasti Astu, Be Well!
> Kauai's Hindu Monastery
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode