Is there an option to disable the automatic calculation while planning a trip?
My problem/Situation: Not all Waypoints have specific names. I want to edit all waypoints so the have nanmes. Everytime I press “enter”, the app starts re-calculating the entire route. This is cumbersome and tiring.
How to temporarily disable that function?
Thanks for any hint and/or workaround.
Regards
Ganz einfach: Im Planungsmodus tippst du auf oben links auf das Kurviger-Symbol, auf “Einstellungen” und deaktivierst “Automatische Neuberechnung”.
Hi @SPKELLER,
No, there is no option to stop Kurviger from calculating a route.
Could you maybe explain a little more detailed what you try to achieve? You can rename your own favorites (locations that you saved in the cloud) in the cloud without adding them to a route.
Have a look here on how that works.
Thanks for offering to help… My problem is: as shown in the picture, there are waypoints have no name. When finalizing the plan, I want to add names which then appear in my tourbook and/or on the navigation display (e.g. TomTom). Therfore, I have to copy the “Adresse” manually into the textbox “Wegpunkt-Name”. After every entry (and hitting enter) the entire route is calculated, even though there are no changes to the route. With 50+ names to enter, it means also 50+ calcaulation cycles.. cumbersome and tiring… Disable calculation for the time of entering the names would be a relieve.
Thanks for clarification. Now I understand were you’re at. Since changing a waypoint name also requires, for example, changes to the turn-by-turn directions, the route must be briefly “recalculated” here. This cannot be disabled. I assume you have a very specific usecase if you have to name 50+ Waypoints?
Usually this recalculation only takes a very short moment. If your routes are very long I would suggest to split them into e.g. day trips.
Maybe change the calculation to “straight line” minimizes the time to wait.
Thank you for the response. It is a long route, indeed. Normally, I plan the entire route in one file to include all the POI and/or scenic routes I might want to visit. As I might change quite a bit in the process, am not paying too much attention to the waypoint names. Later on, when getting closer to “lock the master plan”, am naming the waypoints which stay in the route. After that I start spliting the master file into daily plans. This particaluar master plans covers approx 9000 km and 42 driving days, plus extra days for longer stays (museums, hiking etc), recovering 
and “laundry days”. With the this I have a layout - sort of travel guide - for the trip . However, By their very nature, plans are at the mercy of fate—which is why they end up getting changed from time to time. That’s just how things go with daily schedules! 
Don’t be surprised if Kurviger starts behaving strange when you get close to 9000km. To my knowledge, there is a technical limitation of the underlying technology. There are several threads on the forum discussing this issue. If you encounter such problems, simply split the route in two parts. This is not a bug that can be fixed, it is a limitation of the chosen technology and the SW architecture.
A work around but cumbersome.
That’s right - but “straight line” is not a curvature for the whole route …
Fair enough…
BUT: doing this - recalculate and re-do the turn-by-turn instructions - AT THE END of ALL changes would result in the very same route.
Additionally, the benefits would be 1) not having to wait as a user for each recalc and 2) not using ressources at the routing server for nothing beneficial.
So how about implementing a mode where one can change the route’s details (waypoints, names, exact shaping point locations, etc.) and offering to recalculate ONCE at the end of the required changes!???
This is a good point. The route is just an array of data. If you can use the text editor to change the names in that array when the route is saved as a file, the programmers could use the same principle in the app to change the names without resending the same coordinates to server for recalculation. The server does not need names for the calculation. It is kind of weird that it does not already work like that.