Key problem

Hi guys,

I am facing issues with providing support of buttons on touch devices. I used "onSelect" behavior event before to execute code based on the "select button". This worked fine for physical buttons but caused touchscreens to only execute this method on tap. Now I changed my code to this:

function onKeyPressed(keyEvent) {
if(keyEvent.getKey()==Ui.KEY_ENTER || keyEvent.getKey()==Ui.KEY_START) {
...
return true;
}
}

Unfortunately users of devices like the Forerunner 735xt or 235 are reporting that their button is not working any more. I cannot reproduce this on the simulator and my own watch (Fenix 6) is working fine. Anybody knows what goes wrong here?

Thanks!

Bye

Top Replies

jim_m_58 over 6 years ago in reply to Talkabout +1

onKeyPressed() and onKeyReleased() aren't that consistent between devices as onKey() in my opinion, and can get confused with things like hotkeys.

All Replies

jim_m_58 over 6 years ago

I never use onKeyPressed() or onKeyReleased(), but just onKey(). Maybe try that. Also if you fall through onKey(), be sure to do a return false;

Talkabout over 6 years ago in reply to jim_m_58

Hi Jim,

thanks for the quick answer!

But what exactly is the difference? And is the way I am building my "if"-statement correct or am I missing use cases here?

jim_m_58 over 6 years ago in reply to Talkabout

onKeyPressed() and onKeyReleased() aren't that consistent between devices as onKey() in my opinion, and can get confused with things like hotkeys.

Talkabout over 6 years ago in reply to jim_m_58

Thank you Jim, will try it that way and hope that it will work. In my opinion the simulator needs to show the same behavior, otherwise debugging is really difficult :)

Former Member over 4 years ago in reply to jim_m_58

Just tested on FR 235. onKeyPressed()/onKeyReleased() work in the simulator, but appear to do nothing on the device, onKey() works both on the simulator and the device.

jim_m_58 over 4 years ago in reply to Former Member

Yup, the semi-rounds weren't consistent if I recall (it's been a few years since I checked.)

If you want to try to detect your own long press of buttons, be very, very, very careful (I don't do it at all), because based on the device and the specific button, long press can already have a meaning. And on devices like the high end forerunner and fenix watches, you got hot keys, where the user can define things based on the button and a long press, multiple button presses at the same time, etc.