Last Route
-
Opening the "Last Route" in MRA Mobile (probably no NEXT functionality, but still...) does not open the last opened route, but the last changed route in the planner platform. Now that Next is integrated I think it would be logical to change this to the last route opened for navigation OR the last route changed in the planner (whichever comes last).
-
Last route should be the last opened and not the last edited route (for those with Next).
-
@Con-Hennekens
Now the last completely navigated route is opened. Not the route that was opened last.
(That's my experience...) -
Oh boy, here we go
The amount of discussions about edited vs opened for this button has been immense. The nice thing now is that the button does exactly what the identical button in the website does. I do agree however that with regards to Navigation it makes sense to jump back to the last one you were driving -
I could say more, it would be great to have a question "the last route hasn't been completed, do you want to continue"? I have it in Sygic and it is very useful after a break for a dinner etc - I don't need to seek the route, correct waypoint to start. What do you think?
-
@Bart-DM said in Last Route:
Last route should be the last opened and not the last edited route (for those with Next).
It's more complicated than that. Last opened in the app only? or also last opened in the planner too? I think it makes perfectly sense to consider the "last route", the one that has been edited in planner, if it wasn't superseded by another opened route.
@Corjan-Meijerink said in Last Route:
The amount of discussions about edited vs opened for this button has been immense.
It's not quite often I miss discussions like that
@Corjan-Meijerink said in Last Route:
with regards to Navigation it makes sense to jump back to the last one you were driving
See my comment @Bart-DM. Next is being integrated into Mobile, let's consider it ONE app... Another satisfying solution could be to make it two buttons: "last edited route" and "last navigated route". The button is large enough to be divided in two
-
@Con-Hennekens I like your suggestion