Speeding up app startup with lots of points visible
I have a lot of points stored in various folders. With more than 500 points marked visible starting the app gets more or less a pita (sorry). I see that this is an issue mentioned often and earlier. I just wanted to bring it to your attention again.
I assume startup time until the map gets displayed could be a lot quicker if only "really" visible points get loaded at startup, the rest could be deferred.
This could be achieved retrieving a valid GPS signal at first (fallback: where Locus Map left off last time) and then retrieving the nearest points first until the map with the current zoom is filled or even retrieving all visible points after the map is displayed in a separate thread.
I suppose there is no need in calculationg distances to perfection, just load the points with nearly the same coordinates first, e. g. same degree & minute +/- some epsilon, making it a wee bit more elaborate near a meridian (no trouble if lat/long are stored as float fields as a "select from points where lat between latCurrent-0.005 and latCurrent+0.005 and lon between lonCurrent-0.005 and lonCurrent+0.005").
Or maybe I'm just too naive.