Acknowledged
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.
Parents
  • > 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.

    Revisiting this statement (and my comments about it), now I see that Vivoactive 6 no longer has a button press (or long button press) which is intended to open a context-sensitive menu, unlike almost every other Garmin device in the past. (The one exception was Vivoactive 3, which used a long press of the screen to open a menu)

    Now I have a better understanding of where this comment is coming from, specifically: "we can only have now menus on va6 if we also have this ugly thing on the screen."

    It does seem that Garmin's intention is that every app (native or CIQ) will have to display the action menu indicator if they want to offer the user any kind of context-sensitive menu. (I assume that if the app wishes to display a full-screen menu, then the "standard" way to do this will be via an item in the action menu.)

    I will say that it's still true that nothing prevents you from having a different way to open an action menu, but it's probably not a good idea.

Comment
  • > 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.

    Revisiting this statement (and my comments about it), now I see that Vivoactive 6 no longer has a button press (or long button press) which is intended to open a context-sensitive menu, unlike almost every other Garmin device in the past. (The one exception was Vivoactive 3, which used a long press of the screen to open a menu)

    Now I have a better understanding of where this comment is coming from, specifically: "we can only have now menus on va6 if we also have this ugly thing on the screen."

    It does seem that Garmin's intention is that every app (native or CIQ) will have to display the action menu indicator if they want to offer the user any kind of context-sensitive menu. (I assume that if the app wishes to display a full-screen menu, then the "standard" way to do this will be via an item in the action menu.)

    I will say that it's still true that nothing prevents you from having a different way to open an action menu, but it's probably not a good idea.

Children
No Data