bump
--- In flexcoders@yahoogroups.com, "ben.clinkinbeard" <[EMAIL PROTECTED]> wrote: > > I am noticing some odd behavior adding capture phase event listeners > to TabNavigator. While trying to answer another question > (http://tech.groups.yahoo.com/group/flexcoders/message/84929) I > noticed that this code: > > tabNav.addEventListener(IndexChangedEvent.CHANGE, onChange, true); > > will cause a RTE if onChange()'s event arg is typed as > IndexChangedEvent. As it turns out, listening to the capture phase > causes the listener to receive a regular Event object whose target is > the actual tab you clicked on. Listening to bubble phase produces an > instance of IndexChangedEvent whose target is the actual TabNavigator, > which is what I would think is the expected behavior. > > I am assuming the problem has something to do with the fact that > IndexChangedEvent.CHANGE and Event.CHANGE both evaluate to "change". > Is this expected behavior? I can't quite get my head around why it > would be but that doesn't mean its not. I actually had this problem > with a custom component the other day and ended up changing the > event's string value to avoid the collision. > > Thanks, > Ben >
