This is because of the MetaCard message path. If you click on an object
that's not in a group, the message follows this path and stops when it finds
a handler for the message:
object clicked
card the object is on
all groups on the same card, starting with the group with the highest layer
#
stack the card is in
mainStack (if the stack is a substack)
Home stack
MetaCard engine
If your card doesn't have a mouseUp handler, and a group on the card does,
the group will catch the mouseUp. Putting the empty mouseUp script into the
card was the correct solution if you don't want the group to catch
extraneous mouseUps.
Marni
> -----Original Message-----
> From: thierry douez [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 13, 1999 10:52 AM
> To: [EMAIL PROTECTED]
> Subject: mouseup hierarchy tricky ?
>
>
> Hi all of you,
>
> Could someone enlight me about this behavior :
>
> has a group of buttons and put a script "mouseup" into the
> group itself
> not to duplicate it into all the buttons. This works well .
>
> but, when I click anywhere outside the group, the mouseup
> event is trapped
> by the group script "mouseup"
> if i put an empty script mouseup into the card script, works
> fine again.
>
> don't really understand this ...
>
> thanks for an answer
> thierry
>
> ------------------------------
> thierry douez - IGBMC - France
>
----------------------------------------------------------------------------
--------------------
The views and opinions expressed in this email message are the sender's
own, and do not necessarily represent the views and opinions of Summit
Systems Inc.
