I seem to remember going down this road before which modifying the event handling / dispatching / removing before. It's rolling your own entire eventDispatcher ( IE like starling did) or you'll have to rely on flash player changes which aren't likely.
The argument that was given about not rolling your own dispatcher was all about the speed and efficiency of native Flash Player code vs. the AS code. -Mark On 9/20/13 9:00 AM, "flexcapaci...@gmail.com" <flexcapaci...@gmail.com> wrote: >Would creating an object pooling mechanism for new events improve >performance? For example, if instead of calling new FlexEvent() we called > >var changeEvent:FlexEvent = FlexEvent.getEventFromPool(FlexEvent.Change); > >and then that method checks its object pool for an unused event instead of >creating a new one? > >When looking in Scout there are a lot of the same type of events being >dispatched that don't have any references. This might be something that >might be changed at the Flash Player level?
