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
Parents
  • 1 month ago

    Yeah. My app is a sailing app so it's in a wet environmet. This change to require touches basically disqualifies devices like that for me.

    I know none of this is ideal, but here's a couple of ideas:

    1) You could implement something like the native Strength app on Forerunners, where pressing the START/STOP button actually opens an action menu, which has items for stopping (pausing) the activity and accessing settings. (In hindsight, this type of behaviour is clearly a test run for Garmin's vision of using "discoverable" action menus instead of a universal menu shortcut which involves holding a button)

    Ofc this would suck if the user needs to quickly stop the activity, although they could still do so by pressing START twice

    2) You could use the BACK/LAP button to open an action menu, which would also include an item to take a lap (if your app supports that). This would suck if the user needs to take a lap quickly

Comment
  • 1 month ago

    Yeah. My app is a sailing app so it's in a wet environmet. This change to require touches basically disqualifies devices like that for me.

    I know none of this is ideal, but here's a couple of ideas:

    1) You could implement something like the native Strength app on Forerunners, where pressing the START/STOP button actually opens an action menu, which has items for stopping (pausing) the activity and accessing settings. (In hindsight, this type of behaviour is clearly a test run for Garmin's vision of using "discoverable" action menus instead of a universal menu shortcut which involves holding a button)

    Ofc this would suck if the user needs to quickly stop the activity, although they could still do so by pressing START twice

    2) You could use the BACK/LAP button to open an action menu, which would also include an item to take a lap (if your app supports that). This would suck if the user needs to take a lap quickly

Children
  • 1 month ago in reply to FlowState

    FlowState - Thanks for the ideas.

    I already use the start/stop button to bring up a menu that's different from the one displayed when Menu is used.

    I'm quickly coming to the conclusion that it's not worth any effort to support devices that work like this, particularly since my app is a sailing app so it's used in a wet environmet.