You don’t like the save button in the Dialog or what do you mean with saving option?
Isn’t it good if you can safe your unsaved route only with one tap in this Dialog and you have not to open more dialogs for this Action?
In my opinion it’s fine if you only have to do one tap to save the unsaved route and with an other tap then select your actual prefered target when it differs from the target selected in the Settings for Bringing Back to actual route (These Settings actually are not implemented, but mentioned by devemux86 in the past).
Actual workflow without saving actual route and without selecting preferred target (with number of taps):
Blue Arrow Tap (1 Tap)
The workflow to check or manipulate the target proposed by me is (with number of taps):
a) without saving actual route, check without manipulation of target:
Blue Arrow Long Tap > OK (2 Taps)
b) without saving actual route, check with manipulation of target:
Blue Arrow Long Tap > Select your actual prefered target > OK (3 Taps)
c) with saving actual route, without manipulation of target:
Blue Arrow Long Tap > Save Button Tap > OK (3 Taps)
d) with saving actual route, with manipulation of target:
Blue Arrow Long Tap > Save Button Tap > Select your actual prefered target > OK (4 Taps)
Due to this workflows the Blue Arrow Long Tap perhaps for some users could be the prefered Blue Arrow Action because of Information to the target they will be brought back and with only one more tap they can save the actual route. Is it possible to save the actaul route with less taps?
This Dialog IMHO only makes sense when “Bring Back To”-Settings are implemented.
Blue Arrow Action perhaps is more important when Offline Routing is available. Therefor it’s worth to have a view on user friendly use handling of it.
Sorry for confusing, but it’s hard to describe in english what I mean. Currently I have problems using the Features of the forum. I have to learn much! Though I like the discussion to improve the app. Be free to answer, can respect each answer.
The whole discussion boils down to one question: How should Kurviger treat waypoints that you have “passed” (= left “behind” you) while being off route?
Currently Kurviger skips automatically waypoints that are “behind” you even if you haven’t visited them.
That’s a feature, that could lead to unwanted results in some cases at round trips.
Mario (@SchlesiM) has excellently explained the possible situations above.
The arrow (blue traffic sign) points you back to your planned route.
When you tap on it, it does calculate a way back to your planned route.
IMHO that’s an easy understandable behavior.
Any menu popping up here makes things more complicated and I wouldn’t like that while navigating.
I think, a (relatively) simple and clean solution would be some sort of settings, where you tell Kurviger how to treat waypoints that you haven’t visited.
Something like:
You have lost your route and want a (one time) recalculation - vehicle is possible moving.
Now you want to long press the blue arrow (vehicle may be stopped at a traffic light)
Chances are, that you accidently trigger a short tab
IMHO the one time recalculation feature is only useful if it can be triggered quickly by a short tab.
If you want questions to be asked, then better stop navigation and start it again.
my problem in reality is still that I don’t have a feeling if I’m touching long time or short time, because my gloves not always do what they should do.
So normally I’m pressing the button until I see that something is reacting…therefore I have no feeling for long or short press.
So this way for menu is not my preferred one…
Best regards
juschka
I can confirm that. Long touch operations are quite difficult to perform with gloves (often even a touchpen). I already noticed that when switching the follow mode. So any alternative would be appreciated.
I also prefer Short Tab to Display the Options Menu in big size, but don’t agree with Manfred to stop navigation for the Options menu. I want to do everything while driving.
If used several Times you know the Menus and Position in the Screen anyway by heart and can blind use it.
Long Touch for Automatic calc according to a defined Option in settings additionally is ok… The question is how long is long touch?
And i hope it is available in July when the trip goes to Slowenia.
Context menus on Android are performed usually via long press and actions via tap (if be together).
We haven’t decided yet what to put in it, when to use it, where to put it (depends on 1-2).
As options not changed often while driving belong inside Settings.
Regarding timing, like all features, when it’s designed, implemented and tested can be provided.
normally I would expect that the route is re-calculated to the next waypoint in the planned route when the Button “Skip next waypoint” is used.
Yesterday I had a strange effect when skipping waypoints: I have Skipped all waypoints in Order to get a new route to my planned Destination. But the route was calculated back to the previous planned route, even of there were NO WAYPOINTS any more. I don’t understand why because in this Situation the route should get calculated new and if there ist no more waypoint, then to the Destination.
I wouldn’t call this behaviour rerouting changes the planned route
Maybe your waypoints weren’t necessary, and Kurviger would have taken that route anyway.
But If you don’t want to share your route we can’t know.
For everyone:
Can reproduce the route at home and describe later with *.kurviger files and images what happened. e.g. @SchlesiM’s examples
With just text it’s impossible for us to understand any workflow.
yes that’s generally ok to follow strictly the waypoints (especially when the blue arrow is used). But on Tuesday I had the effect I used the menu to skip waypoints, in fact I had used this several times successively until I had only the destination to go, but the re-calculation was done as if I had not deleted (skipped) the waypoints… that was the weird situation.
maybe this helps a little bit… this is from the GPS recording and the strange thing is that there are gaps of recording… can this maybe be connected to the strange behaviour?
