[fixed] Landmark Open URL Function Missing !!!

[Psyberia-Support]

No no sorry that's not what I wanted to say.
If you display a complete .LDK file, then the loading and displaying of items it contains is postponed after the map is displayed and usable.
Now LDK files are just "containers" allowing you to group various landmarks in a single file, just like KML and GPX do, but with no loading times when you browse it to list items. But once you want to display an item, like a track, that track still need to be loaded to be displayed.

[Yemble]

I agree that is how is should work, but that is not what I am experiencing. If I have a couple of LDK files in Displayed Landmarks, each with a few thousand embedded simple landmarks (not routes), all displayed, AQ shows a white screen for up to a minute on startup before displaying the map. If I remove these landmark files, then the map is displayed within a few seconds of startup.

[Psyberia-Support]

I've made some speed tests to compare both 1.4.x and 2.x versions (using KML files) and it's true that the 1.4 does display the files faster. I'll investigate why it's like that...
Concerning the fact that you LDK files are not loaded after the map is displayed... I've just no idea.

[Yemble]

AQ 2.02 r2982 has fixed the dead route issue and all the usual functionality has been restored. Thank you

The delayed map loading issue remains, however. The text on the white startup screen just says "Restoring Items..." and the length of the delay is proportional to the number of LDK files that appear in the Displayed Landmarks screen, regardless of whether, or not, they are actually selected to be displayed, via the tick.

If I have no LDK files in Displayed Landmarks, then the map displays almost immediately. If it is relevant, I have the files configured to display the embedded landmarks in order of distance from the centre position, rather than in alphabetical order. I also make use of the Display All option.

[Psyberia-Support]

I trust you, I just can't explain that (so many thing I can't explain when the app is running on Android 6....).
I'll close this topic anyway since the open with problem is now fixed, don't hesitate to open another discussion for your problem with the loading time.