Acknowledged
CIQQA-3123

Vivoactive 6 Simulator problems

The Vivoactive 6 simulator does not seem to respond to a Menu command, and only responds to the buttons in a very tiny area along the edge of the button where it meets the body of the watch in the simulator. 

The Vivoactive 5 simulator operates as expected so it looks to me like this is a set of simulator bugs.

Parents
  • Actually all CIQ devices with CIQ 3.4.0 or higher allow you to open an action menu using WatchUi.showActionMenu(), it's just Vivoactive 6 which allows Connect IQ to display the action menu indicator which the user swipes left on to open an action menu, using View.setActionMenuIndicator(). It seems likely this was done because the action menu indicator is the only option for context-sensitive menus on VA6, so they don't want devs to have to reinvent the wheel here.

    For example, on FR955 / FR965 / Fenix 7, there are many native screens where an action menu is opened by pressing START (in this case there will be a button hint next to the START button, but this is just a generic hint that indicates pressing START will do something). In all of these cases, the action menu can also be opened by tapping or swiping left on the button hint.

    I think what's actually unique about VA6 is:

    - it has a dedicated indicator / UI element to  open the action menu

    - there's no other way to open a context-sensitive menu (i.e. no universal shortcut like holding a certain button)

Comment
  • Actually all CIQ devices with CIQ 3.4.0 or higher allow you to open an action menu using WatchUi.showActionMenu(), it's just Vivoactive 6 which allows Connect IQ to display the action menu indicator which the user swipes left on to open an action menu, using View.setActionMenuIndicator(). It seems likely this was done because the action menu indicator is the only option for context-sensitive menus on VA6, so they don't want devs to have to reinvent the wheel here.

    For example, on FR955 / FR965 / Fenix 7, there are many native screens where an action menu is opened by pressing START (in this case there will be a button hint next to the START button, but this is just a generic hint that indicates pressing START will do something). In all of these cases, the action menu can also be opened by tapping or swiping left on the button hint.

    I think what's actually unique about VA6 is:

    - it has a dedicated indicator / UI element to  open the action menu

    - there's no other way to open a context-sensitive menu (i.e. no universal shortcut like holding a certain button)

Children
No Data