Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

AppGameKit Classic Chat / [BUG?] Android Raw Touch on older Android versions

Author
Message
Supertino
6
Years of Service
User Offline
Joined: 22nd Jun 2017
Location: Behind you!
Posted: 13th Apr 2018 19:54
I have three devices.

- Amazon Kindle Fire 5 ( android version 5.1.1 )
- Samsung Mini 4 ( android version 4.4.2 )
- Moto G4 ( android version 7.0 )

In the sample code below the Samsung and Kindle increase the counter by 2 each time you tap the screen and you get two message boxes. The moto works as expect.

This was happening on the last version of AppGameKit and is also happening on the version that was released this week. 2018.04.12

If you uncomment the sync() after Message() it works as expected on the samsung and kindle suggesting something not getting flushed after the usual sync() on older version of android maybe?

Amon
9
Years of Service
User Offline
Joined: 30th May 2014
Location: Shropshire, United Kingdom
Posted: 13th Apr 2018 23:59
Yep. I've got a Galaxy Tab 3 on Android OS 5.1.1 and I get the same as you do.
Imaginations' greatest gift is the knowledge you supply it.
Supertino
6
Years of Service
User Offline
Joined: 22nd Jun 2017
Location: Behind you!
Posted: 16th Apr 2018 10:26
Paul Johnston
TGC Developer
21
Years of Service
User Offline
Joined: 16th Nov 2002
Location: United Kingdom
Posted: 17th Apr 2018 16:01
Thanks, fixed for the next version. Incidentally I got this bug on all devices I tried, even iOS and Android 8.0.
Richard_6
7
Years of Service
User Offline
Joined: 3rd Feb 2017
Location:
Posted: 19th Apr 2018 14:00 Edited at: 19th Apr 2018 14:01
Ah, I was getting crazy to solve this here since my multi-touch game suddenly wasn't working anymore on my iPad.

Paul, when are you planning to release the next version with this fix? Any possible workarounds in this meantime?

Login to post a reply

Server time is: 2024-04-20 13:33:37
Your offset time is: 2024-04-20 13:33:37