I’m personally not sure that MouseEvent actually works. Any case of MouseEvents in the Framework actually dispatch BrowserEvents. The only exception to this case that you will currently find is in TLF where there is code which generates MouseEvents from points.
Check out my browser-event branch for my attempt to make MouseEvents and KeyboardEvents behave the way you’d expect. I’m currently struggling with figuring out how to make artificially created MouseEvents behave properly. Maybe we should compare notes… Harbs > On Jul 25, 2017, at 9:49 PM, Peter Ent <p...@adobe.com.INVALID> wrote: > > I've been doing work with Drag and Drop and that involves mouse events. I'm > wondering if someone could give me a history on the Apache FlexJS MouseEvent? > Specially, its use of localX/Y and screenX/Y. > > I'm wondering why the platform implements do not simply assign their version > of screenX/Y as the screenX/Y values instead of the screenX/Y being getter > functions? > > I've run into cases where the localX/Y == screenX/Y in the FlexJS MouseEvent > but the original event had different values. > > Why would we not want the FlexJS MouseEvent to reflect the platform's mouse > event values? > > SWF: flexJSMouseEvent.screenX = swfMouseEvent.stageX; > JS: flexJSMouseEvent.screenX = jsMouseEvent.pageX; > > Thanks. > Peter Ent > Adobe Systems/Apache Flex Project
