My starting point is as before.... create a basic watch app in Eclipse, using the wizards.
I don't change anything.
I build the app.... with the timeout change, the build now succeeds.
I run the app in the simulator on the Vivoactive HR simulation.
The app that is created presents a graphic of a monkey.
When I hold down the right button a 2 item menu is presented.
If I select Item 1, a message appears in the debug log window indicating that Item 1 was selected.
If I select Item 2, no message appears, though the code indicates that it should.
Instead, the menu shifts up, centering the Item 2 menu item text.
I see no code in the example that causes this behavior
The documentation for the Menu support in the UI does not describe this behavior, or how to control it, though it shows exactly the code that I'm seeing in the project that was created.
I also attempted to use the debugger to follow the code and see what's going on.
The onMenuItem() function is not entered when I select Item 2.
So.... what's happening here, and is it possible to create a menu that does not behave in this way ?
The API documentation for menu, and menuInputDelegate do not describe this behavior.
Is there documentation that describes what to expect from the underlying menu handler ?
I see a parameter called ui.SLIDE_UP that looks suspicious, but it is passed to pushView() so I suspect (though the documentation does not verify) that this applies to how the view is presented over the previous view.
Also....
The debugger does hit the break point that I set inside onMenuItem(), but once the break point is hit, and I attempt to get the code to continue to run, the app in the simulation no longer responds to any button or menu selection.
I hope there's a way to use the debugger to hit a break point, walk through the code, and continue to run until another break point is hit.