Acknowledged
1 month ago
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.

Jeff
  • 28 days ago

    > On a real va6, some of the system menus pushed usnig the menu indicator are full screen menus so this does not look out of place.

    Thanks for mentioning this.

    I take back what I said earlier, in that case. (I wrongly guessed that the real va6 would never push a fullscreen menu using the action menu indicator.)

  • 29 days ago in reply to jrjackson

    This is exactly what I am doing, except I use an input delegate so am catching the KEY_ACTION_MENU, but I simply push my Menu2 rather than using an actual action menu.

    On a real va6, some of the system menus pushed usnig the menu indicator are full screen menus so this does not look out of place.

  • 29 days ago

    Since all I want to do is get to the same menu I use on all other devices it seems the most minimal way of adding support is just the following:

    //In my main View initialize() turn on Action Menu indicator

    if(View has :setActionMenuIndicator) {
       View.setActionMenuIndicator({:enabled=>true});
    }


    //In my view delegate catch the action menu invocation and just create my regular/legacy menu

    function onActionMenu() {
      return onMenu();
    }

    This seems to work fine in the simulator.  Anything I'm not considering with this?  Not seeing a need to use the ActionMenu, ActionMenuItem, ActionMenuDelegate for this.
       
  • 1 month ago in reply to FlowState

    > Therefore, based on presence of View.setActionMenuIndicator I will use ActiveMenu to build my main menu, otherwise I will continue to use Menu or Menu2.

    That is the expectation 

  • 1 month ago

    > So as developers I wonder if we are safe to assume we will see EITHER legacy onMenu() (non-touch or mostly button devices) and onActionMenu() (touch or mostly touch devices). Therefore, based on presence of View.setActionMenuIndicator I will use ActiveMenu to build my main menu, otherwise I will continue to use Menu or Menu2.

    I think that could work.

    You could also check simulator.json to see if onMenu is mentioned in the keys[] or display.behaviors[] arrays.