Restarting route calculation without defining the "To"/"From" positions again
(Copied from the end of another topic which has already been marked "Solved":
https://getsatisfaction.com/locus/top... )
...
I have observed the problem with MapQuest this week too, however I have found the solution myself (switching to Cloudmate).
The situation (and similar situations in the past) led me to the following question:
Is there a way to restart route calculation without defining the "To"/"From" positions again ?
Example:
I want to be navigated to a point. I browse the maps, find the point and in its context menu I choose "Navigate to" and then choose eg. "Fast". However this first route calculation does not succeed for a reason (MapQuest does not work or I have switched off data services by mistake or ...). I immediately correct the problem (eg. switch on WiFi or mobile data). Do I have to define the destination again ?
The same question
Hello Celda,
yes, sorry for a MapQuest. They changed their API from day to day, but in next Locus version (within a few days) it will work again ...
Anyway to topic ... same question (problem) you wrote about, led me to create extra tab "Recently used" in screen where you choose start and target point for navigation. Isn`t this tab helpful?
Hello Celda,
yes, sorry for a MapQuest. They changed their API from day to day, but in next Locus version (within a few days) it will work again ...
Anyway to topic ... same question (problem) you wrote about, led me to create extra tab "Recently used" in screen where you choose start and target point for navigation. Isn`t this tab helpful?
You are right - "Recently used" could help me ! :-)
However, if the initial route calculation does not succeed, after certain timeout you could redisplay the window with "To/From" too, couldn`t you ?
BTW how is "Recently used" internally stored ? (eg. in case I define both "From" and "To" by existing waypoints) Is it just 2 absolute positions (From and To) and a description or dynamic link to waypoints defining From and To or even the whole route found ?
You are right - "Recently used" could help me ! :-)
However, if the initial route calculation does not succeed, after certain timeout you could redisplay the window with "To/From" too, couldn`t you ?
BTW how is "Recently used" internally stored ? (eg. in case I define both "From" and "To" by existing waypoints) Is it just 2 absolute positions (From and To) and a description or dynamic link to waypoints defining From and To or even the whole route found ?
"timeout" ... I agree that some improvement is needed here, I`ll keep this in my mind and will try to improve it
about "Recently used" - there are two "Recently used" tabs.
One is on screen where you choose location for a various places. Here are stored just name, source and coordinates, so you may use them simply later. it`s useful right in cases, when you stop navigation on some point and want to continue later.
Second "Recently used" is at "navigate to" screen and here is stored completely! whole track. It`s mainly for a one usage. You let locus navigate on some place, then you stop this navigation, track disappear from map. If you want continue later, you may use this tab and choose last used track which is just loaded from cache "sd card", so you may continue without need of internet
"timeout" ... I agree that some improvement is needed here, I`ll keep this in my mind and will try to improve it
about "Recently used" - there are two "Recently used" tabs.
One is on screen where you choose location for a various places. Here are stored just name, source and coordinates, so you may use them simply later. it`s useful right in cases, when you stop navigation on some point and want to continue later.
Second "Recently used" is at "navigate to" screen and here is stored completely! whole track. It`s mainly for a one usage. You let locus navigate on some place, then you stop this navigation, track disappear from map. If you want continue later, you may use this tab and choose last used track which is just loaded from cache "sd card", so you may continue without need of internet
>timeout
I think there must be some timeout even now because when no route is found (e.g. MapQuest does not work) I get some message after a while, but the "From/To" window is not opened any more.
>Here are stored just name, source and coordinates, so you may use them simply later
So it is "a static snapshot" of the "From/To" coordinates at the moment, isn`t it ? Example: When I define a wpt called "Target" and set navigation to it, it is stored here as its current coordinates. Another day, when I modify the coordinates of my waypoint "Target" and then choose this stored navigation I will be navigated to the old position, won`t I ? This is not a problem, I just want to know, how the storage is implemented.
>here is stored completely! whole track.
This is another story, I know it and use it from time to time (e.g. when I am going to be navigated abroad where I don`t have a mobile data tariff).
>timeout
I think there must be some timeout even now because when no route is found (e.g. MapQuest does not work) I get some message after a while, but the "From/To" window is not opened any more.
>Here are stored just name, source and coordinates, so you may use them simply later
So it is "a static snapshot" of the "From/To" coordinates at the moment, isn`t it ? Example: When I define a wpt called "Target" and set navigation to it, it is stored here as its current coordinates. Another day, when I modify the coordinates of my waypoint "Target" and then choose this stored navigation I will be navigated to the old position, won`t I ? This is not a problem, I just want to know, how the storage is implemented.
>here is stored completely! whole track.
This is another story, I know it and use it from time to time (e.g. when I am going to be navigated abroad where I don`t have a mobile data tariff).
timeout ... yes, there`s already 30s.
"static snapshot" - exactly
timeout ... yes, there`s already 30s.
"static snapshot" - exactly
Replies have been locked on this page!