[closed] AQ v2 Map Display Delayed Whilst LDK Files Are Loaded

[Yemble]

I've opened this as a separate issue, as requested...

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]

Hi and thanks for opening a new discussion for that, sorry for the troubles.
I haven't found anything strange yet while testing, I'll try to check using the same order as you do.
I'll also try to find a place on the online help to explain how it (should) work.
I'll come back to you soon, sorry for the delay.

[Yemble]

NP, this loading behaviour is consistant across all three of my devices, although the delay is longer on the S3 phones. Note that I am running in off-line mode, if this is relevant, using a cached OSGB full UK map, with one additional overlay (OSGB MiniScale). I don't recall any significant loading delay in AQ v1.4 with the same maps and landmark file sets displayed, albeit in GPX format rather than LDK.

[Yemble]

I have some timings on my S3 phone for loading the following files:

WalkingWorld.ldk - 2.2Mb
GoodBeerGuide.ldk - 1.3Mb
CasqueMark.ldk - 3.5Mb

Startup delay to display map as follows:

5s - no landmarks loaded
17s - WalkingWorld
55s - WalkingWorld + GoodBeerGuide
225s - WalkingWorld + GoodBeerGuide + CasqueMark

The times remain the same regardless of whether, or not, the landmarks are actually displayed (via the tick, rather than UnDisplay).
When the map does display, the landmarks are also displayed immediately.

Note that the phone CPU is not particularly busy whilst the LDK files are being loaded (ie. the phone is not CPU bound).

To be fair, I would not normally have all three landmark files displayed on my phone, normally it would just be WalkingWorld. However, my tablet is a different matter, where all three files would normally be displayed. Start times are faster on the tablet, compared with the phone, but still much slower than in AQ v1.4 for the same set of files in GPX format.

[Psyberia-Support]

Thanks for the update.
Just to be sure, you need to display the whole file to get a delayed loading: long press the .ldk file, and select "Display". It's not the same if you display just the waypoints inside it (for example when selecting "Display all").

[Yemble]

Yes, I have Display All selected, however, this has no bearing upon the load time.

[Psyberia-Support]

In fact, you mustn't select "Display all" to get the delayed loading.
If you display the whole file ("Display" after long pressing the file), then this one will be listed in the "Displayed landmarks", and only it.
If you select "Display al" on the content, then all items will be separately added in the "Displayed landmarks" list, which is what usually takes time, and in this case you don't have a delayed loading...

[Yemble]

Sorry, I've read what you have written several times and it still makes no sense. I want every landmark within each file to be displayed on the map, just like I have always done with AQ v1.4. I don't see that I am doing anything differently, it's just taking a lot longer in AQ v2.

[Yemble]

Ahhh, sussed it. This is the difference between "Display" and "Display All" when first loading an LDX file (or importing a GPX file). The two functions appear to have exactly the same end result on the display, but they are obviously subtly different, as witnessed at load time.

The "Display" option does, infact, load the LDK files after the map when restarting AQ, unlike "Display All" which loads LDK files before the map. The actual load times for both methods seem pretty similar on my tablet.

I must say that I am now wondering what the point of the "Display All" function actually is?

You have to admit that this IS confusing

[Yemble]

There is one problem with this "Display" method for managing LDK files. If you untick the file within Displayed Landmarks, all of the landmarks are hidden, as expected. However, if AQ is restarted, the landmarks become visible again. In other words, the display state is not remembered which seems wrong to me.

[Yemble]

Also, when using the "Display" method, files are listed in Displayed Landmarks by their file name, rather than the more user friendly title field stored withing the original GPX file meta-data. "Display All" uses the latter.

Anyway, why is the load sequence different between these two methods?

[Yemble]

Hi, as you have not commented on my last couple of posts, I am not sure that you have seen them...

The retention of the landmark display status when re-starting AQ is the most important to have fixed, IMHO, in order to make the "Display" method work in the best possible way for the user. The displayed title is cosmetic, but would be a nice to have and is more in keeping with the rest of the system.

Is this something that you can implement?

Do you want me to open a separate case for these?

[Psyberia-Support]

Hi again and sorry for the delay. I did read your posts, just didn't find the time to properly answer.
No need to open another thread, it all linked.

First (the easy part):

if AQ is restarted, the landmarks become visible again.

You're absolutely right, this is not correct. I'll fix that.

when using the "Display" method, files are listed in Displayed Landmarks by their file name, rather than the more user friendly title field stored withing the original GPX file meta-data.

True. I'll change that too.

Then, concerning the difference between "Display" and "Display all", it's a bit more complicated.
In fact, both methods are quite different (it's true that it may be confusing, but both methods make sense when explained).
- The "Display" action on a .LDK file will display the file as a single entity. If you check the "Displayed landmarks" list just after that (from the "Landmarks" menu), you'll see that your .LDK file only takes one line. You can also only change its visibility as a whole. In this case, the restoration at startup is delayed as you've seen.
- The "Display all" action on a group of landmarks (waypoints, tracks, etc) will display all the landmarks independently. The fact that they actually are in a .LDK file or in a regular folder isn't important. It's like if you would have selected "Display" for each of them one after one. In the "Displayed landmarks" you'll have one line for each of them, and you can control their visibility independently and/or remove only some of them.

When selecting "Display all", the application will need to display them as different entities, and have to handle more things than when simply using "Display" on a .LDK file...

Let me know if something isn't clear.

[Yemble]

Just installed the latest beta... brilliant, all points addressed, many thanks