SimpleButton.hitTestState - Why?

[Keslen]

It may be a lack of imagination on my part, but I can't imagine any situation where I would program a Button and not want the hitTestState to be the same as the overState. Why are these separate categories?

[glosrfc]

With a little imagination, it's quite easy to see why:

You might have a textfield on your button but you don't want that to trigger it.

Or you might want to change the appearance of other symbols on the stage.

Or you might want to use the "invisible" button technique to capture a mouse press anywhere on the stage.

Maybe you only want your button to trigger when the mouse is over a smaller part of the button...or the opposite, where the button is triggered while the mouse appears to be still some distance from it.

Or you have an interactive map with buttons positioned tightly alongside each other, or which slightly overlap. To prevent two buttons from being triggered simultaneously, you might scale down the hit areas of each button slightly.