Paul Dupuis wrote:
An argument could be made that a before handler SHOULD NOT execute, but
an after handler SHOULD since the message was sent directly to the
object (i.e. skipping the normal path and hence the before handler.
I believe an argument could be made in the other direction as well, that
all secondary effects of an action should happen whether the action is
triggered by user interaction or via script.
If I use:
send "go next" to stack "SomeStack"
...I would expect the preOpenCard and openCard handlers to trigger just
as naturally as if I'd clicked a button initiating that action.
Personally, it seems most natural that the mechanism for preventing the
triggering of system messages would remain lockMessages.
But that's my own view. It'll be interesting to hear Mark Waddingham's.
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
____________________________________________________________________
ambassa...@fourthworld.com http://www.FourthWorld.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
