That's what I was referring to. So far, I've read three different use cases for removeEventListeners and I'm adding a few more. In my case it would be to remove handlers setup by framework code so that components that can be added to the stage and dragged around the screen without all of their interactions being dispatched all the time. For example, if you add a image, button or text input to the stage and then enable drag and drop you would also be seeing it's mouse over, out, up and down states change as you interacted with it and have to prevent it's focus in and out events from doing things like setting focus on sub components for text input or button emphasis or the drawing of the focus rectangle.
If you were to track the event listeners you would also be to see what listeners are currently added to an object for debugging purposes. This would open up the possibly of being able to see the order they will be dispatched in. On Mon, Dec 9, 2013 at 6:27 AM, Kessler CTR Mark J < [email protected]> wrote: > Well you can add some redundant code to removeAllListeners if you would > like, but we can't modify the flash player code. The dispatching > ultimately gets handled by the player. I made an example[1] a while back > on duplicating the tracking of the event listeners and ultimately it can > remove them all. The last updated code for it should be [2] for now. > > > [1] http://people.apache.org/~mkessler/examples/FLEX-33608/app.swf > [2] > https://github.com/KesslerConsulting/example/commit/30ee4b96911d301ea09516324241c4bc9d734f16 > > -----Original Message----- > From: jude [mailto:[email protected]] > Sent: Monday, December 09, 2013 5:47 AM > To: [email protected] > Subject: Re: Version 4.12 of Apache Flex > > +1 on the skin upgrades. > > Also, implement something like removeAllListeners to a base class such as > UIComponent or possibly have a utility class that has the same effect. I > saw a patch a while back but I don't think it was ever added. >
