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 the previous comments, I was kind of assuming that CIQ will support setActionMenuIndicator() in FR955 and other 5-button touchscreen watches, and that onActionMenu() will work similarly to the native behaviour of the action menu indicator / action menu.

    But perhaps this is a bad assumption since the supported devices section of the setMenuIndicator doc explicitly lists Vivoactive 6 and the announcement for SDK 8.1.1 specifically called out va6 with regards to this function.

    Regardless, I think it still makes sense to look at the behaviour and purpose of the "action menu indicator" on other devices, even if it's not exactly the same on Vivoactive 6, and even if CIQ won't support it in the same way.

Comment
  • 3 months ago

    In the previous comments, I was kind of assuming that CIQ will support setActionMenuIndicator() in FR955 and other 5-button touchscreen watches, and that onActionMenu() will work similarly to the native behaviour of the action menu indicator / action menu.

    But perhaps this is a bad assumption since the supported devices section of the setMenuIndicator doc explicitly lists Vivoactive 6 and the announcement for SDK 8.1.1 specifically called out va6 with regards to this function.

    Regardless, I think it still makes sense to look at the behaviour and purpose of the "action menu indicator" on other devices, even if it's not exactly the same on Vivoactive 6, and even if CIQ won't support it in the same way.

Children
No Data