MenuInputDelegate vs InputDelegate (TouchScreen)

Hi -

I just realised that one of the possible reasons that my app is not recognising the "ENTER" key on the VA when in a Menu is that it was using a MenuInputDelegate instead of the InputDelegate.

on the Simulator, it works correctly (but I think this is a bug)
Steps to reproduce
1) Start activity (press enter key)
2) Pause Activity (press enter key)
3) wait x seconds for the Save/Discard menu to come up
4) User presented with option so Resume / Save / Discard the activity

What happens in the SIM
I press the ENTER Key ( the menu is on the resume menu option), activity resumes. (note that when this happen, I do not see the ENTER key being pressed. no sys.println on the console showing physical key is pressed)

I tap on the resume menu option. Activity resumes

What happens on the watch.
When users press the ENTER key, nothing happens

When user taps on the screen (on the resume menu option), the activity resumes.

Question:
What's the correct method to enable the ENTER key to be utilised during a menu selection (MenuInputDelegate).
The same code works on NON-Touchscreen devices whereby the ENTER key is used to select the menu option.

Thanks

Former Member over 9 years ago

I don't think the enter key is used to select menu items in any of the native menus on touchscreen devices, so I would expect the native menu view available to ConnectIQ to behave the same way.

I would guess this is an issue in the simulator, which should not respond to the enter key on those devices.

Nikeow over 9 years ago

Understand.
So, if my Aim is to enable the EMTER key to function as what I write, how do I go about doing it?
I want the ENTER key to function as the option to enter that menu option.

Former Member over 9 years ago

It is not possible. The native views are exactly the view frameworks that are used for the native menus displayed on the device. If they don't respond to the enter key, there is no way ConnectIQ can get a message when the key is pressed from that view.

Nikeow over 9 years ago

Oh wow. That's a bummer.

Former Member over 9 years ago

You could always create a custom view that looks like a menu and customize the input behavior, but for the sake of a consistent user experience I would think it is best the menus behave the same in and out of ConnectIQ.

Nikeow over 9 years ago

I don't really want to do anything that will add code bloat.
The thing is, users are telling me that in the native Garmin apps, the KEY_ENTER button _does_ function as an enter button To go / select the menu items.

That's y I was surprised and went to take a look.

Can u confirm that the native app also ignores the KEY_ENTER within a menu?

Former Member over 9 years ago

I can confirm that the enter button does not select menu items on the VivoActive.

The Epix uses either touchscreen or buttons for pretty much all its input, so I assume it allows both in menus.

I don't have a 630 on hand, so I can't check its menu behavior. If the behavior of menus differs between the native system menu and CIQ menus, then that would be a bug. The 630 doesn't even really have an enter button though, so I would be pretty surprised if pressing the start button selected menu items.

If there is a difference in behavior, let us know where you are seeing it, and we can evaluate the situation and let the device team know if there is an issue.

Nikeow over 9 years ago

Appreciate you checking. It's very much helpful - for the VA that is.

The FR630 is a really strange watch from a button and touchscreen perspective (based on what I read and some what I write code for)

The bit about the return true apparently did help on the app.

Thanks again!!

travis.vitek over 9 years ago

I don't have a 630 on hand, so I can't check its menu behavior.

Pressing the top-right button (start) on the 630 while in the menus will cause the currently selected activity type to start recording. I've found no context where pressing the top-right button results in an enter key behavior. i.e., If you press the button when entering your weight in My Stats, it will jump out of the menu and start recording an activity.

Pressing the top-right button within an app (the built-in Stress Score app) has no effect. I don't have a HRM with me so I can't test what happens at a confirmation screen, but I believe that nothing happens.

Nikeow over 9 years ago

I can confirm that the enter button does not select menu items on the VivoActive.

If there is a difference in behavior, let us know where you are seeing it, and we can evaluate the situation and let the device team know if there is an issue.

Hi,

Perhaps I don't know how the VA functions when the start button is pressed. Users are telling me that its function is in Starting / Stopping and Resuming (when in native app). (which is what's happening on a F3)

In my app, (function mimics the F3 I have), when user pauses the activity, it will wait a few seconds and then show the save/discard menu option. I use this same menu option for the VA as well.

Does the VA NOT show this menu option? Or does it show a View that has 3 touchscreen points and the ENTER key is still a valid option to be used?