Vivoactive6 simulator: menu key not working

At first glance this seems like a super radical change: Vivoactive 6 is literally the first Garmin watch which doesn't have a universal "menu" button / gesture.

Every other Garmin watch has some sort of universal (or near-universal) gesture to open a context-sensitive menu:

- dedicated physical (or capacitive touch) menu button

- "menu button gesture" corresponding to long press of a certain button (like UP on 5-button watches). (But even on 5-button watches, in *some* cases, long press of UP does something else, like panning/zooming the map faster than normal)

- long-press screen to open menu (Vivoactive 3, as it only has 1 button)

But I know runners who've worn a Garmin for years and are completely unaware that holding UP is supposed to open a context-sensitive menu / settings menu. Obviously there's nothing intuitive about the previous system.

Obviously Garmin noticed this a long time ago, which is why they changed the activity start page so you can just short-press UP to open the menu (and there's an accompanying button hint). Fenix 8 took this further and allowed you to swipe for settings on the activity start page.

Apparently, Vivoactive 6 is taking this even further by ditching the universal menu gesture, and instead showing an on-screen interactive hint (action menu indicator) for *all* context-sensitive menus, which can only be activated by touch.

Ofc 5-button watches which support touch will probably still need a dedicated menu button/gesture, as they're meant to have full (or nearly full) functionality when touch is disabled. But I wonder if the action menu indicator (or something like it) will eventually appear on all Garmin devices.

It seems that any app which implements a context-sensitive menu will be required to use the action menu indicator, as there's no longer a generic way to open a menu by pressing (or long pressing) a physical button

To expand on this, I assume that any app which wants to display a context-sensitive full-screen menu (such as a settings menu) will be "required" to first provide the user with an action menu; the action menu can have an item which opens the full-screen menu (like "Settings").

Or it could also work the way DCR described accessing watch settings, where settings is just another item in the activity/app list. ofc that only works if you're already displaying some kind of menu or list in the first place.

At first glance this seems like a super radical change: Vivoactive 6 is literally the first Garmin watch which doesn't have a universal "menu" button / gesture.

Every other Garmin watch has some sort of universal (or near-universal) gesture to open a context-sensitive menu:

- dedicated physical (or capacitive touch) menu button

- "menu button gesture" corresponding to long press of a certain button (like UP on 5-button watches). (But even on 5-button watches, in *some* cases, long press of UP does something else, like panning/zooming the map faster than normal)

- long-press screen to open menu (Vivoactive 3, as it only has 1 button)

But I know runners who've worn a Garmin for years and are completely unaware that holding UP is supposed to open a context-sensitive menu / settings menu. Obviously there's nothing intuitive about the previous system.

Obviously Garmin noticed this a long time ago, which is why they changed the activity start page so you can just short-press UP to open the menu (and there's an accompanying button hint). Fenix 8 took this further and allowed you to swipe for settings on the activity start page.

Apparently, Vivoactive 6 is taking this even further by ditching the universal menu gesture, and instead showing an on-screen interactive hint (action menu indicator) for *all* context-sensitive menus, which can only be activated by touch.

Ofc 5-button watches which support touch will probably still need a dedicated menu button/gesture, as they're meant to have full (or nearly full) functionality when touch is disabled. But I wonder if the action menu indicator (or something like it) will eventually appear on all Garmin devices.

It seems that any app which implements a context-sensitive menu will be required to use the action menu indicator, as there's no longer a generic way to open a menu by pressing (or long pressing) a physical button

To expand on this, I assume that any app which wants to display a context-sensitive full-screen menu (such as a settings menu) will be "required" to first provide the user with an action menu; the action menu can have an item which opens the full-screen menu (like "Settings").

Or it could also work the way DCR described accessing watch settings, where settings is just another item in the activity/app list. ofc that only works if you're already displaying some kind of menu or list in the first place.