Re-compute
===========
Tested version 1.13.1.1 extensively today when driving by car. Re-compute with MapQuest works great! Also takes my moving direction into acount, so if I am moving away from my destination, it correctly computes proper turns to get back towards my destination (e.g. U-turns and using a roundabout to turn back. Very good!
MapQuest issue
==============
Found one funny thing: MapQuest always computes some distance (100-200 meters) beyond the last point I enter. When I continue with the next point, I get a double line for that distance. See attached track. There are three places you can see that double line. No big deal. Just want to mention it.
Yours/CloudMade/MapQuest selection gone!
========================================
Just installed version 1.13.1.2. Tapping the guiding selection (create route command line, 3rd button from left) used to pop up a menu where I could select Yours/CloudMade/MapQuest. This was still present in version 1.13.1.1, but is gone in version 1.13.1.2. Why? We need that!! The whole point with "Yours" was to be able to create a route with straight lines between the waypoints. We need that feature back. I used it extensively when flying. Also when walking in the mountains or woods without trails, I want a guiding along straight lines.
The new navigation selections (Limited access, Toll road, Unpaved, Ferry) are really great though! Thank you!
Navigation voice
===============
Navigation voice: when I choose a voice, the new selection is not highlighted blue until I quit Locus and restart it. If I just finish navigation (Guiding Off) and reselect navigation, the last selection is used correctly, but the previous selction is still highlighted.
What about including one navigation voice (English) with Locus. It is not straight forward to extract voices correctly from TomTom and other places. I am sure many people would appreciate at least one English voice included. I would suggest "Ken LOUD". I tried a lot of voices and found this one best.
Rejoing route
=============
Yes, still a problem. Worked in about 4 out of 8 cases today (version 1.13.1.1). When "Closest point" does follow, then Locus understands when I am back on track. So the real issue is the fact that the "Nearest point" gets stuck. Would one solution be if Locus executes the "Nearest point" command once in a while (e.g. every 10 seconds) in the background? Could you think of situations where you would not want that to happen?