Need help with Yes/No type menu and Prompt

Former Member
Former Member
Ok .. I have my application and I have a menu of workout items. This is for a Vivoactive HR.

For example ..
<string id="menu_label_w1">0.2 km 15x</string>
<string id="menu_label_w2">0.35 km 13x</string>
<string id="menu_label_w3">0.35 km 6x</string>
<string id="menu_label_w4">0.85 km 7x</string>

That is all fine. But I am running into an issue in that there are 13 'workout' menu items right now and there could be more in the future.
But because I have to scroll down in the menu and it is very touchy .. I often select the wrong one.

So I would like to add a confirmation type prompt .. ie "Do workout 0.2 km 15x ?" with a Yes / No as menu items.

EDIT ... I can do this but have issues getting rid of the menu on a YES selection.

So if the user selects No .. then it would go back to the Workout menu again for selection of the correct workout.
If yes .. it will continue to the main app screen to do the workout.

Just need a bit of help on this one ..

Thanks
Kevin
  • Former Member
    Former Member over 8 years ago
    The biggest problem I have is getting rid of my menus totally when the user selects YES indicating that they have the right workout. I cannot get to the main app screen as my menu is in the way. On yes .. I need to get rid of all menus.

    I think I am stuck between popping and pushing .. I think I am pregnant. :rolleyes:

    For anyone that reads this .. you can do I understand .. Ui.popView(Ui.SLIDE_IMMEDIATE) .. to get out of your menu. I know that helped me.

    I got it working .. but honestly I just liked the one menu rather than 2 with the confirmation. I will just be careful selecting my workout.
  • Former Member
    Former Member over 8 years ago
    If I understand you right, and you have removed the confirmation, then I think you have made the right decision. Other than an important scenario where data may be lost or changed I think it best to code with the assumption that the correct interaction will be made. You don't want to bog down a user, who is interacting correctly, with unnecessary prompts.
  • Former Member
    Former Member over 8 years ago
    If I understand you right, and you have removed the confirmation, then I think you have made the right decision. Other than an important scenario where data may be lost or changed I think it best to code with the assumption that the correct interaction will be made. You don't want to bog down a user, who is interacting correctly, with unnecessary prompts.


    Yes .. removed it as it was only a confirm for a workout selection (which may or may not be correctly chosen). I just did not like that it added almost nothing, other than the yes/no which is not that often of an issue. I have 13 workouts right now (and btw I am the only user), so it is just if I happen to get the wrong one, I just discard the session if one even starts recording at all. So .. it is more of a small inconvenience at worst.

    I have not decided but I may make a submenu .. ie workouts 1-4, 5-8, 9-12, 13-16 (though they would be labelled as needed and not with numbers) in order to eliminate the need to scroll at all. But then I introduce another menu, which I am hesitating on doing. But probably better than the yes/no.

    It is especially a pain in that I am standing on the side of some road looking to go and do my workout, I do not want to be bogged down with a bunch of extra prompts I have to go through. But I did learn a bit about nested menus .. so that in itself was a good thing.
  • Former Member
    Former Member over 8 years ago
    I actually did a much easier fix .. i just moved the 4 workouts that I use most often to the top of the list. Now .. I need very little scrolling.

    I am training for a big race in August so I think this will do it. :cool:

    I think the trick to this is to touch the very far right edge of the VAHR and scroll up and down, that way you can scroll through the menu items without selecting one.
    I wish the Vivoactive HR menu was not so sensitive as this issue would ... not be an issue.