I'm testing a watch app using API 1.3 for the FR235 (running v5.2 firmware) that has a menu and uses the up and down keys. On the FR235, pressing and holding UP key is the menu key. That works fine and onMenu is tripped in the BehaviorDelegate. Unfortunately, the onPreviousPage (UP key) is also fired before the on menu. So the app sees two events when the user is trying to get to the menu and this causes other problems (switching between modes in the watch app). I tried switching to the InputDelegate, but onKey is also getting both the UP button and the MENU button.
When testing in the simulator, it works correctly. But on the actual watch, not so much.
Code is simple and looks like:
function onMenu() {
Routines.getController().action_showMenu();
return true;
}
function onSelect() {
Routines.getController().action_advanceRoutine();
return true;
}
function onNextPage() {
Routines.getController().action_gotoNextRoutine();
return true;
}
function onPreviousPage() {
Routines.getController().action_gotoPrevRoutine();
return true;
}
Any ideas on how I can "detect" when onPreviousPage() is invoked that it's still held down and "on it's way" to being a MENU button and not actually do my onPreviousPage logic?
Gerry
