From c7a55d66951beafc4bc8bc06a09e6555abb04e05 Mon Sep 17 00:00:00 2001 From: sonora Date: Wed, 7 Jan 2015 10:57:41 +0100 Subject: [PATCH] Test build: Try force route re-caculation if stopped due to Issue2515 --- .../net/osmand/plus/views/controls/MapRouteInfoControl.java | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/OsmAnd/src/net/osmand/plus/views/controls/MapRouteInfoControl.java b/OsmAnd/src/net/osmand/plus/views/controls/MapRouteInfoControl.java index f0780d3b95..eb84fa0f41 100644 --- a/OsmAnd/src/net/osmand/plus/views/controls/MapRouteInfoControl.java +++ b/OsmAnd/src/net/osmand/plus/views/controls/MapRouteInfoControl.java @@ -80,6 +80,12 @@ public class MapRouteInfoControl extends MapControls implements IRouteInformatio } else { //TODO: Hardy: Looks like there is a small bug somewhere: Re-selecting the "From" or "To" point during an ongoing route calculation (and only then) seems to only interrupt the ongoing route calculation. but not restart it, if (and only if) a route origin other than "Current position" is set. (Looks like this case is treated like a mere position update in our RoutingHelper, so normally no complete re-calculation is needed.) getTargets().setStartPoint(latlon, true, null); + //--- + //Try force route re-caculation if stopped due to Issue2515 + if (!routingHelper.isRouteBeingCalculated()) { + getTargets().setStartPoint(latlon, true, null); + } + //--- } contextMenu.setLocation(latlon, null); showDialog();