RE: [flexcoders] Re: idiotic flex fires 2 event handlers for buttons of a substate !!!

[Matt Chotin]

Yes, someone pointed this confusion out to us a few weeks ago and I’ve filed a usability bug.  SetEventHandler would be better named AddEventHandler.  When you call Set you do not overwrite a handler that was set in a base state.  What you can do is set the event handler function and then in the function do conditional logic based on the currentState (in addition to the technique you’re doing).   Matt   From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of jpc14_99 Sent: Friday, September 15, 2006 10:06 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: idiotic flex fires 2 event handlers for buttons of a substate !!!   > Maybe you can replace the whole button instead of just the handler. That's what I ended up doing after my timely debugging and it works fine. I was just frustrated because you can switch a handle from the base state just fine, so I saw no reason why you couldn't do likewise to another substate. I cannot think of any reason why you'd ever want flex firing off 2 handlers at the same time. Thanks. __._,_.___ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com SPONSORED LINKS Software development tool Software development Software development services Home design software Software development company Your email settings: Individual Email|Traditional Change settings via the Web (Yahoo! ID required) Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe __,_._,___