Hey,
I tried b338 today and saw that “tap” events are not working any more on Android - “touch” events do work - and both are fine on iOS and simulator. (device is a galaxy tab 2.2)
I am registering the listener to an object (dunno if it makes a difference) and I can see in logcat that the two toWindow events gets delivered.
[lua]self._someCrazyImage:addEventListener(“tap”, self)[/lua]
cheers! [import]uid: 11772 topic_id: 8623 reply_id: 308623[/import]
Ugh - we will look into it asap.
c. [import]uid: 24 topic_id: 8623 reply_id: 31018[/import]
okay, cool thanks carlos!
I checked out b309 and they are not working there too, so it must have happend quite a while ago. [import]uid: 11772 topic_id: 8623 reply_id: 31072[/import]
team, how’s your bug-hunt going?
i tried to verify the bug and it only occurs if the “tap” gets registered to self
[lua]somerect:addEventListener(“tap”,tapfunction)[/lua]
work, nevertheless this is quite a problem since we choose a OO-like architecture for the app…
oh and it’s also the same with b268
cheers! [import]uid: 11772 topic_id: 8623 reply_id: 32071[/import]
any update on this? [import]uid: 11772 topic_id: 8623 reply_id: 35045[/import]
I’m experiencing the same problem with the latest stable build (484)
Any solutions yet?
In my code, the format offered by aleeri still does not work on Android. Works fine on iOS and on the Corona simulator. [import]uid: 33608 topic_id: 8623 reply_id: 38600[/import]
Hi,
it’s fixed in b507:
Android: Ensure that tap events are called when mulitouch is active. (507) - case 5390
a workaround in 484 is to not use multitouch [import]uid: 11772 topic_id: 8623 reply_id: 38668[/import]
Thanks! It works. Almost gave up on making an android version for my app…
Using the last daily build all tap events work fine. [import]uid: 33608 topic_id: 8623 reply_id: 38728[/import]