On 2/2/13 11:11 PM, Robert Sneidar wrote:
Ok now I see. If the button is NOT a part of the group, the card gets the message first, THEN any background group. I have to say though that is an odd duck.
It provides HC compatibility, with some differences. Since HC didn't have "groups" per se, we didn't have to worry about where the messages went after they hit the background. They just went right to the stack. LiveCode can have several groups, installed at different levels, so the path becomes more complex.
Objects will always pass their messages to their owners. If they are in a group, then the group gets the message regardless of its level (and if that group is in another group, then the enclosing group gets the message next.) It gets snarly after that, depending on the setting of backgroundbehavior.
Also, my example is causing LC to lock up after two or three times, and then attempting to select something. I'm not even going to try and find out why. <sigh>
Probably something in the IDE. It intercepts every message and user action. Suspending it might work.
-- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.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
