It actually is a bit counterintuitive that a card can receive a preOpenStack message. After all, the whole (ostensible) idea is that "preOpenstack" is sent before the stack opens, so how could there even be a card to send that message to.
It is all mainly a matter of drawing, though, not what is actually is existence. The wording is a bit misleading is all... Craig -----Original Message----- From: Mark Wieder <mwie...@ahsoftware.net> To: use-livecode <use-livecode@lists.runrev.com> Sent: Sun, Sep 7, 2014 11:23 am Subject: Re: preOpenStack Terence Heaford <t.heaford@...> writes: > Putting it in the card script does seem to be the answer. > > Had a quick look in the dictionary and I couldn’t find where it says do not put it in the stack script. > The dictionary just says the message is sent to the destination card when you open a stack. As you yourself quoted, "the message is sent to the destination *card*". The card has the first crack at handling the message. If the handler is in the stack script then it's accessible at the root of the message path from any stack in the ecosystem. Placing it in the card script localizes its effect. -- Mark Wieder ahsoftw...@gmail.com _______________________________________________ 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
