> Since the onRollOver state of clip A is being > fired, it blocks > the event of clip B or C's events from ever being fired. > > How do you get around this?
Your solution is to nest two child instances within your outer movie clip (clipA), and define event handlers for them (but not for the outer clip). Instead of assigning handler script to the movie clip itself, assign it to a nested clip called something like "hotSpot" whose depth is lower than that of your button (clipB). Note this hot spot clip may need to be invisible or a custom shape and size. If you need one handler's code to execute from the other handler, just invoke it directly (example: hotSpot.onRollOver();). If you need identical code to execute from both handlers, create a separate function and invoke it from each handler when the proper event is detected. - Jason _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
