Acknowledged
3 months ago
CIQQA-3097

Vivoactive6 simulator: menu key not working

In the simulator for the new Vivoactive6, the menu key (m) is not working.

Also the image only shows a black and white scheme of the watch, but maybe that's intended?

the-ninth
Parents
  • 3 months ago

    PS: also I think the View.setActionMenuIndicator is a cool step into the direction of having easily accessible indicators for behaviors (instead of inputs), that are also in line with the native UI of the watch. Would be great to have something like that for other behaviors as well, and also a view loop that just visually aligns with however native view loops work for the device.

    I agree with this, although I think setActionMenuIndicator was implemented for vivoactive6 out of necessity, not convenience. (As the standard way to provide a context-sensitive menu on va6 seems to be display an action menu indicator, and va6 does not have a universal menu button/touch gesture.)

    For example, fr955 arguably has an "action menu indicator" - it just happens to look exactly the same as the START button hint that's used in other cases.

    When an action menu is available on fr955:

    - the standard START button hint is displayed

    - the user can open the action menu by swiping left (just like va6), tapping on the button hint, or pressing START

    So the action menu functionality on fr955 is *almost* like the action menu functionality on VA6 except that fr955 doesn't have a unique UI hint and there's more than one way to open the action menu.

    Nonetheless, setActionMenuIndicator() seems to be dedicated to VA6 (for now).

    Not only do the docs for setActionMenuIndicator() say "since 5.1.1", but the supported devices list is limited to VA6. (If this was intended eventually to be universal functionality, I would've expected there to be no supported devices list at all.)

    Then again, maybe I'm wrong and this will be brought to FR955 and other 5-button watches.

Comment
  • 3 months ago

    PS: also I think the View.setActionMenuIndicator is a cool step into the direction of having easily accessible indicators for behaviors (instead of inputs), that are also in line with the native UI of the watch. Would be great to have something like that for other behaviors as well, and also a view loop that just visually aligns with however native view loops work for the device.

    I agree with this, although I think setActionMenuIndicator was implemented for vivoactive6 out of necessity, not convenience. (As the standard way to provide a context-sensitive menu on va6 seems to be display an action menu indicator, and va6 does not have a universal menu button/touch gesture.)

    For example, fr955 arguably has an "action menu indicator" - it just happens to look exactly the same as the START button hint that's used in other cases.

    When an action menu is available on fr955:

    - the standard START button hint is displayed

    - the user can open the action menu by swiping left (just like va6), tapping on the button hint, or pressing START

    So the action menu functionality on fr955 is *almost* like the action menu functionality on VA6 except that fr955 doesn't have a unique UI hint and there's more than one way to open the action menu.

    Nonetheless, setActionMenuIndicator() seems to be dedicated to VA6 (for now).

    Not only do the docs for setActionMenuIndicator() say "since 5.1.1", but the supported devices list is limited to VA6. (If this was intended eventually to be universal functionality, I would've expected there to be no supported devices list at all.)

    Then again, maybe I'm wrong and this will be brought to FR955 and other 5-button watches.

Children
No Data