>>My question to you would be, why would you expect a button to broadcast that >>it being rolled over? There is no standard UI reason for it. The only real >>action that a standard button is good for is clicking.
Hmmm. I would tend to disagree with that. I think for the same reasons you would want a custom-made button to broadcast it. Even with standard UI buttons, I can think of uses for onPress, onReleaseOutside, onRollOver, etc. What would make an mx button any different? Imagine a fast-forward button for an animation which you hold down to activate, and then release to deactivate. I mean, there are a million uses IMO. I think if I were to venture a guess, the real reason is what Mike was suggesting: Macromedia chose the lowest common denominator, redundant code, simplicity, etc. Unless there ARE ways to broadcast these other events from MX UI buttons, which I don't know about. Jason Merrill | E-Learning Solutions | icfconsulting.com NOTICE: This message is for the designated recipient only and may contain privileged or confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of this e-mail by you is prohibited. _______________________________________________ Flashcoders@chattyfig.figleaf.com 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
