A common Event interface makes sense. I don't think it will fully solve
the problem. Folks will still expect a common base class and make
mistakes. It is a rough point in FlexJS right now, but I think there are
bigger fish to fry. Folks writing handlers in MXML will not have this
problem as oft
I looked back through the commit log because I knew there were reasons for
having org.apache.flex.events.MouseEvent extend
org.apache.flex.Events.Event rather than flash.mouseEvent. There were
cases where was code that was expecting a generic
org.apache.flex.events.Event and having org.apache.flex.
But if flex.MouseEvent extended flash.MouseEvent and implemented the flex.Event
interface, it would be both flash.MouseEvent as well as flex.Event ...
Chris
Von: Harbs
Gesendet: Freitag, 15. Juli 2016 13:58:03
An: dev@flex.apache.org
Betreff: Re: [FlexJS] Mouse
Well how about having an Interface "Event" and every form of event implementing
that? I think a MouseEvent should be an Event.
Chris
Von: yishayw
Gesendet: Freitag, 15. Juli 2016 11:52:17
An: dev@flex.apache.org
Betreff: Re: [FlexJS] MouseEvent extends flash ev
