Started by Menion, March 18, 2019, 14:52:24
0 Members and 1 Guest are viewing this topic.
Quote from: menion on April 20, 2019, 22:04:30Thousands? This happens for all of your tracks? I tough we solved one similar issue in the latest version, so this should happen only for newly modified tracks!With my work on many places last weeks, I have little mess in head what and where is already fixed. Anyway, I'll definitely publish regular Beta version next week, so if with this beta problem still appear, I'll add into the app method to fix this problem for the whole database.
Quote from: menion on April 17, 2019, 00:04:06Hello slarti76,hmm, what is your settings > maps > advanced features > Increase map resolution?Seems this setting affect lower limits of "zoom lock".
QuoteI believe that in the special alpha version we test here on the forum, this issue no longer exists.
Quote from: menion on April 22, 2019, 09:45:32Hmm "nearest" in sorting of tracks should really be nearest. Even a "map center" used in case of disabled GPS is little weird (most probably should be "last known GPS location").
Quote from: menion on April 22, 2019, 06:45:58hmm firstly because in the search screen is in "Track around" visible "My location", it means you have GPS enabled, at least Locus thinks it. Otherwise "Map center" should be in this field.In sort by nearest, the same system is used. So if GPS is enabled, the last known location is used, otherwise, map center is used.To be true, I see no reason why it should give incorrect results, just check this GPS on/off state, thanks.