corrected bug in reverse geocoder timeout handler
This commit is contained in:
parent
f273f0cfc5
commit
4ff4fcf516
@ -200,7 +200,7 @@ _showReverseResults_Timeout: function(response, parameters) {
|
|||||||
if(!parameters.do_fallback)
|
if(!parameters.do_fallback)
|
||||||
return;
|
return;
|
||||||
|
|
||||||
updateLocation(parameters.marker_id);
|
OSRM.Geocoder.updateLocation(parameters.marker_id);
|
||||||
}
|
}
|
||||||
|
|
||||||
};
|
};
|
@ -72,6 +72,7 @@ showRoute: function(response) {
|
|||||||
return;
|
return;
|
||||||
|
|
||||||
OSRM.G.via_points = response.via_points.slice(0);
|
OSRM.G.via_points = response.via_points.slice(0);
|
||||||
|
console.log(OSRM.G.via_points);
|
||||||
if(response.status == 207) {
|
if(response.status == 207) {
|
||||||
OSRM.RoutingGeometry.showNA();
|
OSRM.RoutingGeometry.showNA();
|
||||||
OSRM.RoutingNoNames.showNA();
|
OSRM.RoutingNoNames.showNA();
|
||||||
|
Loading…
Reference in New Issue
Block a user