Richard. I understand the reordering of the layers in the hierarchy. That is not the issue. If you modify the handler:
on mousemove newMouseH, newMouseV if the mouseLoc is within the rect of me then put newMouseH, newMouseV end mousemove Even with backGroundBehavior set to "true", the message now only fires when the cursor is within the rect. Like it should. It is a matter of, er, control, not message passing. The constraint to be within the rect implies that the control is just what it seems to be, that is, only as large as it seems to be. This regardless of any change in the hierarchy. The group does not "take over" the whole card in the sense that you imply, unless (not impossible at all) I misunderstand you. Craig -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/mouseMove-backgoundBehavior-tp4714294p4714314.html Sent from the Revolution - User mailing list archive at Nabble.com. _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
