On Mon, Oct 20, 2014 at 4:02 PM, Alex Harui <aha...@adobe.com> wrote:
> > > On 10/19/14, 2:33 AM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: > > > >I will sort out the MouseEvent issue next. > > The MouseEvent change broke some MXML compiles and list selection. Sorry about that. > If you > haven’t made progress on it I’ll try to get it working. I figure you > might be busy prepping for your talk tomorrow. > > I just checked in a fix that removes the need for throwing a different event type (mouseOut vs. mouseOut_) http://git-wip-us.apache.org/repos/asf/flex-asjs/commit/85988f92 Please see if this fixes the issue. > I still want to know what scenario showed the need for this change, > although I had wondered whether we would eventually end up needing it. > My usecase: I need to create a simple button that has various states of its skin. Up/out, over, down. I want to listen to the mouse event in each platform (flash.events.MouseEvent vs. goog.events.Event) and set the state of the skin. I assume that I need to attach the mouse event handlers and in those handlers, set the state of the skin. Since the skin class contains the drawing code (as AS3 API calls or MXMLG style code), I need to cross-compile the skin class. So, my mouseevents needs wrappers so that I can list to the wrapped events on both flash and js and react to them in the skin class. Thanks, Om > > -Alex > >
