Hi Greg,
don't know if is related to this, but a problem I found with MoudseEvents
was on iOS Safari and Chrome, using a MouseEvent.MOUSE_OVER.
makes the user have to make an additional touch to trigger click on
buttons. For this reason in Jewel ToolTip I had to avoid mouse over for iOS
with this:
if(OSUtils.getOS() != OSUtils.IOS_OS)
{
IEventDispatcher(_strand).addEventListener(MouseEvent.MOUSE_OVER,
rollOverHandler, false);
}
maybe is not a problem with iOS as I thought but a problem with royale, and
is related to the issues you're describing here. Makes sense?
thanks
El mié., 10 abr. 2019 a las 1:32, Greg Dove (<[email protected]>)
escribió:
> I just made a change in the javascript MouseEvent support, which avoids a
> try/catch on every 'createMouseEvent', and also avoids a dependency on
> MouseEventInit 'converter' class and an associated Language.as coercion. I
> believe this should speed things up slightly for that code.
>
> One thing I observed, and I wanted to check on...
> for
> @royaleignorecoercion window.MouseEventInit
> the 'window' part is not present when the compiler is checking against the
> window.MouseEventInit type in the AsIsEmitter.
>
> so: @royaleignorecoercion window.MouseEventInit does not work
> but: @royaleignorecoercion MouseEventInit does work
>
> for ignoring coercion on :
> params as window.MouseEventInit
>
> Is the above as intended/correct ?
> I made a change in the code that gets this to work - it was not previously
> working to avoid the coercion in the framework MouseEventInit 'converter'
> class (which I think is now no longer needed, unless it is useful for some
> non-framework use)
>
--
Carlos Rovira
http://about.me/carlosrovira
