Acknowledged
3 months ago
CIQQA-3101

bug: vivoactive6 unusable

setActionMenuIndicator

vivoactive6 is so unbaked, there are more bugs than things that work, that I decided to stop supporting it until (if ever) it'll be fixed.

see some of the bugs I already opened:

https://forums.garmin.com/developer/connect-iq/i/bug-reports/bug-vivoactive6-button-area-inconsistent-with-visual-in-simulator

https://forums.garmin.com/developer/connect-iq/i/bug-reports/bug-position-enablelocationevents-crashes-in-vivoactive6

There are lot more, but honestly I don't feel like putting more energy into opening bug reports when clearly Garmin again haven't tried anything out before releasing it.

I'll give a few clues here:

- setActionMenuIndicator(null) doesn't behave as it's supposed to according to the docs.
- in some cases calling setActionMenuIndicator multiple times crashes the simulator: https://forums.garmin.com/developer/connect-iq/i/bug-reports/bug-repeated-call-of-setactionmenuindicator-crashes-simulator
- setActionMenuIndicator as opposed to what it's name hints does not only enable or disable the indicator, but also enables or disables whether the swipe triggers onActionMenu. While I can kind of understand if this was a deliberate decision, I am not sure if it was, and I am not sure if it's a good idea that we can only have now menus on va6 if we also have this ugly thing on the screen. In other words it might be a good idea to make it possible to enable the event triggering onActionMenu without the need to display the indicator.
flocsy🤠
Parents
  • 3 months ago

    > In other words it might be a good idea to make it possible to enable the event triggering onActionMenu without the need to display the indicator.

    If you want to have your own non-standard way of opening an action menu, nothing prevents you from responding to literally any input and calling showActionMenu() (as could've been done in the past.)

    In other words, the *purpose* of onActionMenu is to allow apps to respond to the standard "left-swipe on action indicator" gesture. If you don't want to show the indicator, there's no need for onActionMenu.

Comment
  • 3 months ago

    > In other words it might be a good idea to make it possible to enable the event triggering onActionMenu without the need to display the indicator.

    If you want to have your own non-standard way of opening an action menu, nothing prevents you from responding to literally any input and calling showActionMenu() (as could've been done in the past.)

    In other words, the *purpose* of onActionMenu is to allow apps to respond to the standard "left-swipe on action indicator" gesture. If you don't want to show the indicator, there's no need for onActionMenu.

Children
No Data