>>This leads to the odd effect, that if you have a mouseUp handler in
>>the ancestor, then it will work if there is a mouseDown handler in
>>the subObject, attached as behavior, but will be ignored, if the
>>subObject contains no mouse-events-handlers.
>>Also, the mouseUp handler in the ancestor can be activated, by
>>attaching to the sprite, yet another object, which qualifies for
>>the survey.
>>
>>So if there is any object on a sprite, that triggers the
>>mouse-event mechanism, then the _sprite_ will receive the events,
>>and as a result, any object in the scriptInstanceList, will receive
>>the events, and consequently the events will be trapped by the
>>proper handlers, no matter how deeply nested in ancestors they may
>>be.
>>
>>Jakob
>
>
>And, there are actually two different 'sets' of mouse events.
>MouseUp, MouseDown, and MouseUpOutside seem to be independent of
>MouseEnter, MouseLeave, MouseWithin.
>
>So while the ancestor will get the mouseDown if there is a mouseUp
>in the subObject, it still won't get mouseEnter/Leave/Within until
>the subObject gets one of that set as well.
>
>roymeo
So, wanting to confirm your findings, I opened both mine and Andrews
testbeds, and none of them showed the "missing events" scenario
anymore!!!
I haven't the foggiest what has changed on my machine.
What I seem to be looking at here it not a consistent pattern, but
rather a periodic thing.
???, Jakob
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
