agwells / dotdash-keyboard-android

The world's most popular open source Morse code keyboard for Android! (probably)
GNU General Public License v3.0
32 stars 4 forks source link

Cheat Sheet doesn't appear in Android 4 #9

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. swipe upward from within keyboard area
2. nothing happens
3.

What is the expected output? What do you see instead?
expect to see cheatsheet

What version of the product are you using? On what operating system?
1.1.4 on nexus s cm9v7 stock kernel

Please provide any additional information below.
side-swiping function works fine

Original issue reported on code.google.com by david8bl...@gmail.com on 26 Apr 2012 at 3:35

GoogleCodeExporter commented 9 years ago
I noticed this same issue on a friend's phone that was running Android 4, so 
this seems to be a problem with Android 4 generally. (Cyanogen 9 is is based on 
Android 4.0.)

Unfortunately I don't have ready access to an Android 4 device for an extended 
period of time to debug this (I use an LG Optimus One running 2.3.3), and I 
can't get swipes to work correctly in the emulator for any version of the OS, 
so I haven't been able to fix this issue yet.

Marked "Priority-Critical" because the Cheat Sheet is critical for anyone who 
hasn't memorized Morse code (which is pretty much everyone!)

Original comment by aaronwells on 2 Sep 2012 at 11:19

GoogleCodeExporter commented 9 years ago
I managed to get ICS installed on my LG P500, replicated this issue, and fixed 
it. Previously I was detecting a "swipe up off the keyboard" by looking for a 
MotionEvent with the y < 0. ICS apparently stopped sending MotionEvents once y 
hit 0, so it never got to this point. So, I changed it to y <= 10 instead, and 
that works. Although I suppose there's still the possibility that it may not 
work if a person swipes up very quickly, has a screen with a large resolution, 
and/or their system is running slowly, all of which I'm guessing could cause it 
to skip intermediate MotionEvents. I'll do some testing on a tablet to be sure, 
but for now I'm calling this fixed.

Original comment by aaronwells on 14 Sep 2012 at 12:11