I wouldn't mind looking into that. Maybe using Dictionary's/Map's to group the data better. But I like the idea to only have it enabled exactly where it's needed. My proof of concept code was a bit overkill to make feasibility testing easier.
More idea's for it would be great. I did make a runonce eventlistener that worked well. It removed itself after one run. -Mark -----Original Message----- From: Alex Harui [mailto:[email protected]] Sent: Monday, December 09, 2013 12:35 PM To: [email protected] Subject: Re: Version 4.12 of Apache Flex But I just had a thought: maybe the goal of this feature isn't to solve removing event listeners in the framework code, but in the application developer's code. Maybe we can create a utility class that acts as the proxy and tracks addEventListener calls. Then it is more pay-as-you-go. Use it if you really need it but the framework isn't burdened by it.
smime.p7s
Description: S/MIME cryptographic signature
