Last post by Geooh GO -
Nothing looks like a problem with settings.
No, deleting the Install list isn't the same for the test. I'm trying to determine whether the caches are a problem or the Install list itself has an issue. By putting caches in a separate list removes the Install list concern. I have many more caches in my Install list, but it opens nicely as shown in the video I attached. Maybe the event caches are the issue so if in another list they show the same slow opening, then I would focus on caches.
To experiment, you could try transferring all the caches to another offline test, both Full and Lite, to see if the behavior changes. Other than that I can't think of a cause.
Would deleting the @install get the same result that you are looking for? I have done this and now there is only 7 caches in the list and the error is still there...
Last post by Geooh GO -
Have you turned on the Download Cache Description Images setting in the Geocaches section? If you export settings, I could review them.
To experiment, you could try transferring all the caches to another offline test, both Full and Lite, to see if the behavior changes. Other than that I can't think of a cause.
Last post by Geooh GO -
What happens if you turn off the distance sorting for the Install list? It will take some time to obtain the coordinates of each cache before sorting. And that activity is occurring while building the list for display. I may have to force a sort delay until the list is fully rendered.
Last post by picht -
Hi I haven't been able to figure out why or when, but I have a screenvideo of when it doesn't work. Also note how long it takes from the download finishes and until the @install list is loaded
Last post by Geooh GO -
The number of caches in the Install list shouldn't be a problem, but maybe there is something I don't see. I have 20 in my list.
Last post by picht -
I just did some more testing:
I deleted the @intall Now it works sometimes and sometimes it doesn't. I will see if I can do some more testing and make it reproducible. Maybe the amount of caches in the @install has something to do with it...