Ticket Created
over 4 years ago

WERETECH-9013

Vivoactive 4S swipe identified as a key pressed

At least on the Vivoactive 4S, since I wasn't able to test this out on other devices, there seems to be an undocumented / unwanted behavior that is not directly visible when testing in the emulator.

While developing Monky (https://github.com/vladmunteanu/monky), I had to adjust one of the minigames so that it checks for a key pressed event instead of a swipe right, because when the app ran on the actual watch, it would trigger the onKey event, instead of onSwipe. (https://github.com/vladmunteanu/monky/blob/37fae93329cd7875d9d3c05c9a64c6cffd4cee07/source/SwipeGame/SwipeGameDelegate.mc#L17)

If intended, the documentation should at least be changed to reflect this when implementing an InputDelegate. 

vsm
Parents
  • 4 months ago

     I don't know what was ever actioned as part of this ticket (if anything), but I'm seeing this problem on newer devices now, including the Forerunner 965 and Epix (Gen 2). On those two devices, when using an InputDelegate object, a swipe left to right does not trigger a call to the onSwipe() function and instead triggers a call to onKey() with a key attribute set to WatchUi.KEY_ESC. All other swipe actions follow the expected flow.

Comment
  • 4 months ago

     I don't know what was ever actioned as part of this ticket (if anything), but I'm seeing this problem on newer devices now, including the Forerunner 965 and Epix (Gen 2). On those two devices, when using an InputDelegate object, a swipe left to right does not trigger a call to the onSwipe() function and instead triggers a call to onKey() with a key attribute set to WatchUi.KEY_ESC. All other swipe actions follow the expected flow.

Children
  • 4 months ago in reply to Brandon.ConnectIQ

    Yes, this is happening on production firmware for the FR965 and Epix (Gen 2). In the case of the Epix, this happens on latest stable and on latest beta on actual devices (it's fine in the simulator).

    I can create a new bug report, if you'd like. But, that said, it's incredibly frustrating as it is so hard to know if a new bug report should be created or not, without any visibility into the status of fixes. From my perspective, this bug seems to still be open with no fixes or follow up reported here and the problem I have run into is the exact same as what reported; specifically (and only) the left-to-right swipe.

  • 4 months ago in reply to dbrobert

    I'll create a ticket to have this checked. I'd recommend creating a separate bug report for things like this in the future since it's probably unrelated to the original report here and it may have completely been missed. Are you seeing this problem on production firmware?