While navigating in “strict navigation mode” I discovered the effect that when pressing the navigation button, the actual route is cancelled, pressing again the navigation button drops “the knowledge” of already visited waypoints and starts the navigation again from the beginning.
Pressing the navigation button can also happen unwillingly. I would therefore propose (maybe this is only necessary in strict navigation mode) to stop an already started navigation only by long-press the navigation button and ask before “Want to stop navigation?” YES/NO. Yes - stops actual tour and shows planning mode, No - navigation proceeds. Long-pressing a button normally happens willingly. Short-press the navigation button could only switch between navigation mode and Planning/Overview Mode where the map/route can be zoomed, wp’s can be added or deleted, but an already started navigation doesn’t get interrupted or cancelled.
I am not a native english speaker. If it is not pursuable, please tell what I should explain better.
Don’t know if this is technically possible: maybe an additional idea for more fail safe handling in case of unexpected app closing or by user failure: I guess the already visited waypoints are stored in an array. Why not writing the actual route incl. this array into a local file and when Kurviger starts again, check for the temporary file and ask “a started route was found, reload it YES/NO?” YES: reload and when pressing navigation button, guide to the next unvisited waypoint. NO: drop the temporary tour file.