Yes, the swipe-detection logic in the Android version appears to have problems on some (many?) phones. Not on my Moto G5, but there have already been too many complaints to ignore, and it's only been out a few days.StreakyCobra wrote: ↑Thu Feb 27, 2020 10:31 pmOn another topic I have the feeling that high-res skins have issue registering some key presses. With the size 2 I don't have any problem at all, with size 6 there are some miss from time to time, and with size 12 it's hard to use, a non-negligible number of keys are missed. I noticed that with size 12 a slight swipe left or right on a key show the "print-out", that's something that I can't reproduce on size 2.
If I have to guess I would either say it can be due to a fixed (size-independent) number of pixels defining the swipe distance, or to the loading/copy of active layer key (taking more time in high-res) interfering with the handling of key presses. But I haven't got time to look at your code, so those are just suppositions.
I just uploaded a new build with the swipe-to-switch and n-key rollover logic removed. I'll put them back once I figure out what's wrong. I have a feeling I'll end up getting rid of Android's swipe recognizer and implementing my own pan recognition instead, to make it work like the iOS version, where the new rollover and swipe/pan don't seem to be causing any problems.
It is possible that the skin resolution plays a part. If the swipe recognizer uses a threshold defined in terms of logical pixels instead of absolute screen coordinates, that would be problematic, because Free42 transforms the coordinate system to make the skin fit. That would be seriously lame, but if there's one thing my UI work on Free42 has taught me, it is that Android really is surprisingly lame in some areas. But you have to row with the oars you have, I guess.