The route is restored after a properly exiting the app. In contrast, the route is lost if the app was terminated.
Steps to reproduce:
create route
optional
a) exit app properly
b) restart app
start navigation
app crashes, is terminated by the operating system (HTC Desire X: only 756MB of RAM) or is terminated via the Task Manager
restart app
with 2.: route is restored and navigation can be continued
without 2.: no or an old route --> current route has to be re-created
Solution approach:
Point 2 suggests that the route is saved when exiting. Add these function direct after a route was created. Then, the current route can be restored whatever happens next.
Need to think it more, as route is not only created once, but can be modified also far too many times while the app is active and saving continuously is not nice for I/O performance.
MY solution: ALWAYS “exporting” (= saving) a new route immediately after creating it - it’s only a few steps to do and I do it without long thinking about.
If app or OS crashes, it’s easy to “import” the route and decide to start from the beginning or from my position.
(That’s a reason, why you as developers may think about renaming “export” and “import” in “eport / save” or “export / backup” and “import / restore” - perhaps this would show the usage of these options in a more intuitive way.)
If changing an existing (which means: formerly imported) route, saving wouid be even more comfortable, if there’ll be a function like mentioned in this discussion some day (good to know that’s already on the list of future changes ).
).
