That would make sense, but it would be up to the Player team since EventDispatcher is a Player class. The Flex team can lobby the Player team for new features, but we don't get everything we ask for. Gordon Smith Adobe Flex SDK Team
________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of ben.clinkinbeard Sent: Wednesday, November 28, 2007 12:35 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Am I the only one who wishes EventDispatcher exposed its listeners? Why in subclasses and not EventDispatcher itself? Ben --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "Gordon Smith" <[EMAIL PROTECTED]> wrote: > > > Does anyone from Adobe have info on why its not and/or if it might be > someday? > > The Player's EventDispatcher class doesn't provide this capability, > probably because it isn't part of the Document Object Model Level 3 > Events Specification. (The Player obviously keeps a list of listeners, > but this is done in C++ code and the list isn't exposed in > ActionScript.) However, I suppose the framework could accomplish what > you want by overriding addEventListener() and removeEventListener() in > every subclass of EventDispatcher to keep track of the listeners. Please > file an enhancement request at http://bugs.adobe.com/flex. <http://bugs.adobe.com/flex.> > > Gordon Smith > Adobe Flex SDK Team > > ________________________________ > > From: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> [mailto:flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> ] On > Behalf Of ben.clinkinbeard > Sent: Wednesday, November 28, 2007 6:04 AM > To: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] Am I the only one who wishes EventDispatcher > exposed its listeners? > > > > Sometimes it would be really nice be able to access a list of > currently attached listeners by doing something like > myButton.listeners. Having that return a collection of objects that > expose the event type and handler method would be nice and it doesn't > seem like it would be that hard to implement since they're obviously > already kept track of somewhere. > > Does anybody else wish this was provided? Does anyone from Adobe have > info on why its not and/or if it might be someday? > > Thanks, > Ben >