flash Q
Out of context: Reply #5
- Started
- Last post
- 10 Responses
- davi-t0
resizing the hot spot isn't going to work since u have to deal with the 'layering' of the button hit areas.
The easiest workaround for this (not the best solution), is to create another big ass invisible button on top of ALL of the other buttons that covers all of the other buttons hit areas. Since this 'big ass button' is on top of the other buttons, it will override all of the other buttons. But u also want to make sure that all of ur buttons (including the new big ass button) shouldn't reach to the far ends of the stage...so u can have 'somewhat' of a rollout trigger. So when u rollover one of the image buttons, it will activate the big ass button, and the big ass button will take care of all of the rollout shit.
For example:
// code for an image button.
image_btn1.onRollOver=function...
// doExpand() would be however u r triggering that MC to expand.//Code for big ass button.
bigAss_btn.onRollOut=function...// currentImage.doSlideBack() would be whatever current image slide is expanded. doSlideBack() would be however you are making the expanded state retract.
Obviously, you have to tweak this code and replace the functions with your own code but that 'does' work. Basically, what's happening with ur current hit areas are that the other hit areas are on a layer above the current expanding hit area, so u WILL still trigger those hit spots. Another solution would be to use swapDepths() but I'm not sure how you feel with using that. An even better solution would be to create an array of all of the buttons, and when you rollover one, it disables the rest of the buttons temporarily (btnArray.enabled=false;)...roll... out will reset (ie. enable) all of the buttons again. Hope that helps.
-davi-t