Comments on: Quickfix to enable touch of EaselJS-DisplayObjects in CocoonJS

By: nick

nick — Sat, 21 Feb 2015 00:24:00 +0000

Hi. I’m trying to use this and having no luck.
On iOS everything in cocoonjs works fine. On Android its firing events after touching anywhere on the stage.
I’m including the fix script after my easeljs one.
I have createjs.Touch.enable(stage); enabled.
I’m using easeljs-0.7.1.

Is Android 4.1.1 just too old?

By: Leandro

Leandro — Thu, 17 Jul 2014 08:28:33 +0000

I cant get this fix work for me. Doesnt work the touch event for button.Is this correct way to catch button click/touch event?:
play.addEventListener(“click”, function(e)
{
console.log(“click”);
});

When I click on button catches the event of stage touch.

By: TheManuz

TheManuz — Mon, 26 May 2014 10:06:29 +0000

Thank you very much, it was simple and worked fine!

By: Jimmy

Jimmy — Wed, 21 May 2014 10:59:36 +0000

This fix doesn’t seem to work with the cdn / minified version of CreateJS?

By: Bitrogue

Bitrogue — Sun, 20 Apr 2014 16:27:30 +0000

I’m interested! I do not own a device that would have this problem for debugging (have to rely on feedback from released app) and any kind of quickfix would be awesome as do not have need for complicated touch detection (only rectangles).

By: Vince Wong

Vince Wong — Sat, 19 Apr 2014 08:10:52 +0000

P.S. The “window.onload = fixCocoonEaselJSStageTouch” at the bottom of the touch fix should probably be replaced with “window.addEventListener(‘load’, fixCocoonEaselJSStageTouch);”. This would prevent overwriting of any existing global event handler, and also prevent the risk of being overwritten by another global event handler!

By: Vince Wong

Vince Wong — Sat, 19 Apr 2014 08:07:22 +0000

I’ve had a similar problem: on Android 4.4.2, hit detection for touch events works fine; however, on Android 4.0.3, I’m getting unpredictable results.

Sometimes, I have the problem you reported where touch events are firing on display objects that aren’t beneath the touch location (some object always seems to be hit, and it doesn’t seem related to its position relative to the touch location). However, the majority of times I’ve tried it on Android 4.0.3, a touch event never fires, even if an object appears beneath the touch location.

I’ve traced the issue to createjs.Container.prototype._getObjectsUnderPoint (Stage inherits from Container). Without the above touch fix, x and y passed into this function are always 0, so the touch fix is required. In the case where no events fire, _getObjectsUnderPoint seems to be returning null always. I can only *assume* that in the case where events are firing erroneously, the function is returning objects it shouldn’t be (false positives).

I’ve further traced this to the way the function performs hit detection i.e. by drawing each child to a canvas (with appropriate transform matrix), and then testing whether the alpha channel is > 1 (see _testHit). For some reason, this is going wrong on some Android versions. I’ve not been able to determine why, so my rather unsatisfactory workaround is to replace this hit test mechanism with a faster, but more rudimentary hit test where I assume each child display object is a rectangle. I obviously have to take scaling and registration points into account. I can post this somewhere if you’re interested?

By: Bitrogue

Bitrogue — Tue, 15 Apr 2014 10:53:02 +0000

Works fine on iOS and most Android devices, but some have rather interesting problem where my sprites with onclick function seem to take over the whole canvas?

By: Vince Wong

Vince Wong — Mon, 07 Apr 2014 10:42:59 +0000

You’ve been a massive help – thanks.

By: ramesh

ramesh — Wed, 26 Feb 2014 11:59:50 +0000

EaselJS Button events are not working with your code. it is working only stage events.