Ok, thanks Alex.
-Mark
On Mon, Dec 9, 2013 at 5:40 PM, Alex Harui <aha...@adobe.com> wrote:
> True, but in the five minutes I've spent thinking about this, I'm thinking
> this is for listeners added by a developer's AS code, not by code
> generated by MXML or by the framework, and it will be up to the developer
> to be disciplined enough to use it.
>
> So, if instead of writing: foo.addEventListener("event", someHandler)
> you instead write: EventListenerTracker.addTrackedEventListener(foo,
> "event", someHandler)
> you can later call EventListenerTracker.removeAllEventListeners(foo,
> "event").
>
> And by using addTrackedEventListener and not calling the API
> addEventListener, it is easy for the developer to grep their code to make
> sure everybody is using it.
>
> Anyway, I'm not going to spend time on it, so good luck and have fun if
> you do.
>
> -Alex
>
> On 12/9/13 2:34 PM, "Mark Kessler" <kesslerconsult...@gmail.com> wrote:
>
> >Just a side thought on your proxy idea. The only complication to it is
> >this... We could have one that can be enabled at anytime, but it would
> >only
> >have visibility over what has happened since it was enabled. I like the
> >idea, just need to find an angle that works and provides the functionality
> >as well.
> >
> >
> >
> >-Mark
>
>
