I have one remark : The map zoom level indication is nice. For example "2/5 (13)" means you are currently displaying the map at zoom level 13, but this map can be seen from zoom level 12 to 16. Fine, but with On-board maps it seems I only get "2/5" , the absolute zoom level between parenthesis is not displayed

More importantly, I would like to make some suggestions concerning Route navigation:
The only way left in version 1.4.9, to follow a Route is "Auto target closest" which does not make any sense to me, for following a Route. The concept of a route is that you go from WP1 to WP2 to WP3 etc. or backwards (from WP3 to WP2 to WP1). If I am at WP1, using my compass, I fail to see how does "auto target closest" help me in finding my way = the next target WP?? The target will always be WP1 as it is always the closest … not very helpful. So I suggest these changes in AQ for the Routes:
• Remove option "Auto target closest"
• Add 2 options (which existed somehow in v 1.4.8): "Auto target following" & "Auto target preceding", with a common setting = the min distance at which the next WP on the route is selected. For example, with "Auto target following" & threshold = 50m, as soon as I am at less than 50m from WP1, the target WP indicated by the compass becomes automatically WP2. OK?
• I suggest you also add two buttons (capabilities): "Target Next WP" & "Target previous WP" so that hikers can adjust their navigation according to terrain conditions (obstacles, misplaced WP).
With my previous example: if a user selects "Auto target following" & threshold = 50m, and he is walking with WP3 for example as target. At a certain point, when he is still farther than 50m from WP3, he realizes that, WP3 is misplaced, and it is much simpler to skip WP3 and target directly WP4, then he could instruct his AQ navigator to "target next Wp". Ok?
• I also suggest to implement a warning of some sort (voice announcement, or beep) each time a target WP is reached and the next one is selected.
Finally I think you could correct a small (but annoying) bug: When I browse the content of a route, I see the waypoints correctly numbered ("Waypoint 1", "Waypoint 2", "Waypoint 3", etc.). However the Compass details window always calls the current target "Waypoint" without the number! so it is impossible to know, from the Compass details window which Waypoint on the route is currently the target.
Thanks again! I hope I am not asking too much.
Congratulations again for this great software!
Marc