You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I discovered yesterday the distance measurement tool. There it is possible to move the via points on the map.
In the standard navigation interface I am not able to change the the position of the viapoint. If this would be possible, the users would have the advantage of routeplanning of the distance measurement tool to do at first a rough planning and than make a precise planning.
The text was updated successfully, but these errors were encountered:
Thank you, I have tapped so often on this flag, but I never got the menue.
Von: Alexander Heinlein <notifications@github.com>
Gesendet: Freitag, 26. April 2019 10:35
An: osmandapp/Osmand <Osmand@noreply.github.com>
Cc: cannothing <ich@stephan-zitzmann.de>; Author <author@noreply.github.com>
Betreff: Re: [osmandapp/Osmand] Via points drag and dropable (#6872)
Via points can already be moved. Tap on a via point and select Actions -> Change marker position.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#6872 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/ACBCJRUCPJ4I4N4QXZDHV6LPSK5DJANCNFSM4HITF7NA> .
The icon of this action is a bit misleading. Maybe we can use the crosshair from the measurement tool instead?
vshcherb
added
the
Nice to Have
Should be fixed but there is no priority or no possibility to fix it within current horizon planning
label
Apr 29, 2019
I discovered yesterday the distance measurement tool. There it is possible to move the via points on the map.
In the standard navigation interface I am not able to change the the position of the viapoint. If this would be possible, the users would have the advantage of routeplanning of the distance measurement tool to do at first a rough planning and than make a precise planning.
The text was updated successfully, but these errors were encountered: