That wasn't specifically my thinking but that seems like it would be a super useful benefit of having that info available. I honestly can't remember every situation that has made me want this functionality but the most recent time was when I was trying to determine if a certain function had been registered as a listener yet. hasEventListener() is useless if you have potentially more than one listener. I was concerned that calling addEventListener() again would result in the handler firing multiple times, until I realized EventDispatcher has built-in protection against that.
I suppose we could monkey-patch a listeners collection... dare me? :) Ben --- In [email protected], "Doug McCune" <[EMAIL PROTECTED]> wrote: > > I can see this functionality being useful for various reasons. Ben, are you > thinking you want to track down any listeners that are left over that are > preventing garbage collection? > > Doug > > On 11/28/07, ben.clinkinbeard <[EMAIL PROTECTED]> wrote: > > > > 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 > > > > > > >
