App: Navigation actions menu

[devemux86]

@linux-user

Is Skip next waypoint more important than the other actions.
What if skip next waypoint would be a check box as well, which would be cleared after pressing OK ?

That’s was exactly my initial idea and implementation! A list of equal check boxes where everybody can check whatever wishes. “Skip” is just one of them, cleared each time.

Indeed an option should not be more prominent than others, as everyone has different needs and preferences.

@diesel6876

Also ich finde es gut wenn “Skip next Waypolnt” so wie es abgebildet ein extra Button ist.

If you mean an extra button below, with ok / cancel, that’s not optimal:

• Dialog buttons should have minimal text, “Skip next waypoint” is very large text.
• In future will have more actions, cannot have buttons for each in dialog buttons.

[devemux86]

Another idea is to have navigation actions as a buttons list, like the route actions seen above.

In that case would need to find an elegant way to inform inside the buttons their on / off state.

[Uli_LH]

@diesel6876

Also ich finde es gut wenn “Skip next Waypolnt” so wie es abgebildet ein extra Button ist.

I understand @diesel6876 in the way, that it is GOOD exactly LIKE IT IS in the last picture!

[linux-user]

@devemux86

Another idea is to have navigation actions as a buttons list, like the route actions seen above.
In that case would need to find an elegant way to inform inside the buttons their on / off state.

That’s really a matter of taste.
Then you would have to change the text, dependent on the state of the buttons (don’t know if this is possible)

I personally prefer the check-box version.

• disadvantage: One more click
• advantage: No unintentional action that you can’t revert.

Manfred

[devemux86]

@linux-user’s idea (and mine initial) with check boxes would be:

Check boxes & current implementation have 1 extra step (press OK).

[devemux86]

Implementation via 1 click buttons could be:

(on / off text representation can be also something else)

[chrisjk]

1. I like the informative header.
2. I suggest differentiating what I would call “Actions” such as Skip next waypoint from “Options” such as Rerouting. This could be done by using quite large icons for “Actions” and text for “Options” as at present. Since one cannot use the screen for anything else while this dialogue is showing, the dialogue could be made larger if need be.
3. I would like to see an additional “Action” for cancelling the route - “clearing” in Kurviger terminology - on this dialogue screen.

[SchlesiM]

@linux-user

What if skip next waypoint would be a check box as well, which would be cleared after pressing OK ?
What do others think?

I don’t like the idea to handle “skip next waypoint” with a check box. It should be a button like shown in devemux86’s example.

[SchlesiM]

@devemux86

Implementation via 1 click buttons could be:

(on / off text representation can be also something else)

That would be a good alternative!

[devemux86]

@chrisjk

I would like to see an additional “Action” for cancelling the route - “clearing” in Kurviger terminology - on this dialogue screen.

This menu is meant more for navigation tasks, to be done efficiently while navigation continues.
What is the purpose for clear route (i.e. stop navigation) and not use the current available ways?

[chrisjk]

It is marginally quicker for one and would also be consistent with the interface in Locus Map Pro which is the other navigation app I use. I do appreciate that this is not necessarily a factor in your thinking however!

[devemux86]

@chrisjk

I do appreciate that this is not necessarily a factor in your thinking however!

Let’s see what can get in that dialog.
We certainly discuss all user ideas here!

Such clear route action, stops navigation and removes the route from map, without questions.
Alternatives would be use navigation button and clear route in various places (e.g. left menu).

[Uli_LH]

Regarding the design of “Skip next waypoint” entry, don’t have strong opinions, but if asked:

a) “Action” (immediate response of app) or “Decision” (needs a second tap to confirm?
-> Decision: It needs one more tap, but enables control and revision if decision was made by mistake;
skipping a waypoint by accident (and perhaps not noticed) may cause much irritation, and the decision to skip next waypoint is nothing you do frequently, so one more necessary tap should not be a strong argument against.

b) Check box (set a check mark) or check line?
-> Check box: Check boxes are more consistent with all over design of app? Or planned to revise design in general?

[devemux86]

@Uli_LH

Decision : It needs one more tap, but enables control and revision if decision was made by mistake;
skipping a waypoint by accident (and perhaps not noticed) may cause much irritation, and the decision to skip next waypoint is nothing you do frequently, so one more necessary tap should not be a strong argument against.

That’s why my preference remains the above suggestion with all being check boxes.

My 2nd preference is with being one click buttons (seen above) like in route actions.

And need to consider that more actions will come, so interface needs UI consistency.

[SchlesiM]

I also think it should be: buttons for actions (like “skip next waypoint”), check boxes for settings/options (like “rerouting”).

[Uli_LH]

@devemux86

That’s why my preference remains the above suggestion with all being check boxes.

As justified before I would support THIS way …

[devemux86]

Note that all can be considered actions (e.g. disable rerouting) and all being options if want to provide extra security check via OK.

Thing is that mixing different controls in a (small) mobile interface can produce alien results…

[devemux86]

Until find a more universal solution, can continue with following in portrait / landscape:

[linux-user]

@devemux86

Note that all can be considered actions (e.g. disable rerouting) and all being options if want to provide extra security check via OK.

You can think in this way:

• If you need to store the state, than it is probably an option (=> check box)
• If it is a one time action with no state being stored, than it is probably an action (=> button)

Manfred

[boldtrn]

@devemux86

Implementation via 1 click buttons could be:

I think this option is not ideal, because people have to read the on and off state of the button and cannot use checkboxes. People are used to checkboxes for these things.

@devemux86

Until find a more universal solution, can continue with following in portrait / landscape

I think this would be my favorite approach for now . We can always improve it