Acknowledged
CIQQA-3113

bug: swipe right on the left side of the screen triggers onKey(KEY_ESC)

I noticed this with my app in simulator (fr955, SDK 8.1.1), and then I checked it with the Input sample and it also reproduces it, so it's clearly a bug both in the simulator and even on real devices (tested on real fr965). A similar bug was already reported 4 years ago: https://forums.garmin.com/developer/connect-iq/i/bug-reports/vivoactive-4s-swipe-identified-as-a-key-pressed

To reproduce:

- run the Input sample from the SDK on fr955 in the simulator.

- swipe right in a way that you touch in the middle or the right side of the screen => correctly, only swipe event is triggered

- swipe right touching in the left side of the screen => onKey(KEY_ESC) is triggered (It's not clear when this happens, in the Input sample it looks like sometimes this only happens every 2nd time you swipe on the left side of the screen)

flocsy🤠
Parents

  • +1 for this. I use swipes to increment/decrement values. Swiping right from too far on the left side of the screen results in closing the app. I only want the physical button to close the app - it's currently not possible to prevent this behavior despite returning true in onSwipe(). The key event type and key are identical regardless of whether this faulty swipe is performed or the physical button is pressed. Because they are indistinguishable, the only workaround seems to be to not even use the physical back button (KEY_ESC) to exit the app. This might be acceptable if it weren't incredibly confusing to end users! What is the alternative here?

Comment

  • +1 for this. I use swipes to increment/decrement values. Swiping right from too far on the left side of the screen results in closing the app. I only want the physical button to close the app - it's currently not possible to prevent this behavior despite returning true in onSwipe(). The key event type and key are identical regardless of whether this faulty swipe is performed or the physical button is pressed. Because they are indistinguishable, the only workaround seems to be to not even use the physical back button (KEY_ESC) to exit the app. This might be acceptable if it weren't incredibly confusing to end users! What is the alternative here?

Children
No Data