Martin Wood schrieb:
So you have something like this :
MC_A --¬ (uses mouse handlers)
MC_B (also uses mouse handlers)
Where A is B's parent but A has some handlers defined and none of the
handlers in B will work.
The way around it is to introduce a common parent to A and B which has
no mouse handling, its just a container. So A is no longer the parent
of B
CONTAINER --¬
MC_A (contains some mouse handlers)
MC_B (contains other mouse handlers)
then both A and B's handlers will work.
Yes, that unfortunately is the only way to go - Director btw does this
much better: With Lingo you can pass every event, so it reaches all
objects that want to receive them...
But one more comment on the method above:
Assume you have a onMouseEnter/onMouseLeave method on a background mc
within your container mc, and then place button mcs above this
background mc which want to receive on release events, then when the
mouse pointer hovers over such a button mc, the background mc will
receive a onMouseLeave-event, even though in fact the pointer still is
"within" the background area...
Regards,
Roman.
--
-------------------------------------------------------------------
gosub communications gmbh | fredersdorfer str. 10 | 10243 berlin
t [030] 29 66 88 81 | f [030] 29 66 88 84 | http://www.gosub.de
-------------------------------------------------------------------
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
