(A/B) Well: The motivation behind A/B was to try to get rid of the intermediate transport mode dialogue which some people seemed to not like. If we leave that in place, there is also no need to move the GPX routing, so we can keep our action bars shorter ... :)
Querying the navigation profile only at startup time may not be to good either for 2 reasons: It is probably annoying to be asked everytime at startup. And if you want to later change the transport means, if would be annoying und unconventional to then have to exit the app and restart ...?!
I am fine with the interim dialogue, probably no hard reason to change it...
(D) If you hit "Define view" then change your current viewing profile in the interim dialogue, let's just switch the profile (same as if the user selected the quick-changer, I guess). Still better than a user changing some widget-appearances in default mode, then wondering why this is not visible once they start navigating (because they did not understand the profile-dependency of the map screen appearance at all). In the fashion I suggest with (D), I guess they would get the notion that the profile question at navigation time and at screen-apearance-config time are somehow related...
Nico, completely agree with you, we should add one more option "Set as starting point". You must have gotten me wrong, all that happened was a text label change (in English): "Directions" will now start the navigation (someone even suggested "Navigate", but this would not less well cover the "Show on map" option). And "Add as waypoint" now simply says "Set as destination" as long as there is no destination (and no waypoint) set. (Was fomerly hidden in this case).
Both destination and waypoints (and the future starting point) must consistently be "add-able" by tapping on a map point, by using the "Use location" contect menu, and by using the favorites or any of the search result screens. That's just consistent, nothing wrong with this.
I suggest we just convert the current "show route from here" to "Set as starting point"? (with no automatic subsequent routing, that would have to be invoked after via "Directions" and after a destination and all waypoints are also set)?
Please note one additional bug I discovered on the way: Currently if you have waypoints set, then invoke "Directions" from the map content menu, the route is correctly calculated taking all the waypoints into account. But if you have waypoints set, then invoke "Directions" via the favorites or a search result screen, not just the currentl destination is overwritten (which would be expected), but the waypoints are (silently) deleted, and the route goes straight to the new destination. An annoying bug if you had configured lots of waypoints.