Well, attempting to optimize scrollBar performance I’ve discovered that some event won’t dispatch - I went all though that’s even life with debugger, and, at some point it was like this:
private const _scrollEvent:ScrollEvent = new ScrollEvent(ScrollEvent.SCROLL);
public override function set scrollRect(value:Rectangle):void
{
super.scrollRect = value;
trace(super.hasEventListener(ScrollEvent.SCROLL)); // true
super.dispatchEvent(this._scrollEvent);
}
in ScrollEvent
public override function clone():Event { return this; }
and the handler:
this._scrollBar.addEventListener(ScrollEvent.SCROLL, this.scrollHandler);
private function scrollHandler(event:Event):void
{
trace(event); // called only once...
}
I never call myself nothing like stopPropagation() or stopImmediatePropagation(), in fact, I don’t really care about the event itself, for me it may be null - I don’t need the contents of the event at all, but the scrollHandler() in such situation isn’t getting called…
In .NET events commonly have property “Handled” this property is there to tell whether the event was already processed by a handler or not. However, you, as a developer have control over it - you may decide whether to process it further or not, but it seems like in AS3 you must bloat the player’s memory with piles of useless clones of same event…
Any reasonable explanation to why it is like this in AS3?
