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

    > 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,

    In the native UI of other devices like fr955, the action menu indicator is a button hint next to the START button (at the top right of the screen). (Yes, this button hint is also used for other purposes in the native UI.)

    When that button hint is displayed (and an action menu is available), then an action menu can be opened by:

    - tapping the button hint

    - swiping left (from the button hint or just below it)

    - pressing START

    Crucially, this hint is always displayed in the native UI when an action menu is available.

    So I do think it's logical and intentional that the presence of the action menu indicator is tied to the left-swipe gesture to open the action menu. (At least it makes sense to me in the context of similar behaviour in fr955)

    Maybe the confusing part is that it's called an "indicator" but it also "does" something?

Comment
  • 3 months ago

    > 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,

    In the native UI of other devices like fr955, the action menu indicator is a button hint next to the START button (at the top right of the screen). (Yes, this button hint is also used for other purposes in the native UI.)

    When that button hint is displayed (and an action menu is available), then an action menu can be opened by:

    - tapping the button hint

    - swiping left (from the button hint or just below it)

    - pressing START

    Crucially, this hint is always displayed in the native UI when an action menu is available.

    So I do think it's logical and intentional that the presence of the action menu indicator is tied to the left-swipe gesture to open the action menu. (At least it makes sense to me in the context of similar behaviour in fr955)

    Maybe the confusing part is that it's called an "indicator" but it also "does" something?

Children
No Data