# Small button on large button quirk?

**URL:** <https://forum.kirupa.com/t/small-button-on-large-button-quirk/215417>\
**Category:** Uncategorized\
**Created:** [February 7, 2007, 5:02am UTC](https://forum.kirupa.com/t/small-button-on-large-button-quirk/215417 "2007-02-07T05:02:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![iphotostuff](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/iphotostuff/32/2368_2.png) [@iphotostuff](https://forum.kirupa.com/u/iphotostuff)\
**Post date:** [February 7, 2007, 5:02am UTC](https://forum.kirupa.com/t/small-button-on-large-button-quirk/215417/1 "2007-02-07T05:02:39Z")

</div>

Okay, I know that this is going to be a dimwitted question, but I have a button that is 100x100 pixels, and on top (not inside, these are different bts) of it I have a button 20x20 pixels. I have an onMouseOut command on the 100x100 that makes the 20x20 \_alpha = 0; Perhaps you can see my dilema. When I roll ONTO the 20x20 button that is still within the parameters of the 100x100, the 100x100 registers an “onMouseOut” state which makes the button that I want to press invisible. Is there ANY way to retard that operation? I really only want the OUT state to register when my mouse moves outside of its walls. I have thought of hitTest, but dont’ think it will work in this case because it is the mouse position that I am concerned with. Any thoughts? Sorry if this seems silly.

-i