Several waypoint problems
Hello,
just a few problems with waypoints I have encountered (1.16.3):
1. Moving geocache waypoint to a different category which contains one with the same name (duplicate one) freezes the GUI - the replacement dialog pops up but nothing can be selected and the app freezes - Android offers force close after some time (after which Locus still runs, but the waypoint category list is empty - luckilly only until Locus restart). During copy, the action can be selected and the process seems to work.
Workaround for now: Select the points, export visible, Import to the second category, delete in original category.
2. When skipping geocaches during import, additional waypoints are added to the list as extra points (is it intentional)?
Workaround for now: Do not keep any "normal waypoints" in the category, select a filter for this waypoint type and delete them manually after import.
3. In night mode the (especially geocaching) icons are too bright (because they are in original colours). Maybe instead of inverting the colours, brightness could be reduced and white parts of waypoint icon could be made black?
Workaround: Use Chainfire3D night mode or Screen Filter to reduce the brightness of waypoints.
The same problem 
Hi,
thank you for very complex report
1. fixed
2. fixed
3. it`s more for new idea then as error report. Anyway I think that "Screen filter" is quite good solution ;)
About first two items. They`re almost for sure fixed but they`re in quite complex part of application so if there still be an issue, feel free to contact me immediately
Hi,
thank you for very complex report
1. fixed
2. fixed
3. it`s more for new idea then as error report. Anyway I think that "Screen filter" is quite good solution ;)
About first two items. They`re almost for sure fixed but they`re in quite complex part of application so if there still be an issue, feel free to contact me immediately
Hi (this time hopefully from correct account), I have checked the test version (1.16.3.2) and this is the result
1. Works, seems fixed
2. Possibly fixed, but final waypoint imported from GeoGet database is still imported (but it has name set in GeoGet - FI - instead of FI2R4YR, which I suppose is the way how you detect dependent waypoints). It would require changing the export code to add this information if it is missing in the dependent waypoint.
3. OK, just letting you know.
4. BTW, there seems to persist the issue with date parsing, the dates for geocaches imported from GeoGet database plugin have still creation date 1970-01-01, but the question is, if this is your problem or broken plugin (it worked in old versions of Locus, before fixing broken dates in exports, if I remember correctly)?
Hi (this time hopefully from correct account), I have checked the test version (1.16.3.2) and this is the result
1. Works, seems fixed
2. Possibly fixed, but final waypoint imported from GeoGet database is still imported (but it has name set in GeoGet - FI - instead of FI2R4YR, which I suppose is the way how you detect dependent waypoints). It would require changing the export code to add this information if it is missing in the dependent waypoint.
3. OK, just letting you know.
4. BTW, there seems to persist the issue with date parsing, the dates for geocaches imported from GeoGet database plugin have still creation date 1970-01-01, but the question is, if this is your problem or broken plugin (it worked in old versions of Locus, before fixing broken dates in exports, if I remember correctly)?
Hi Pavel,
yes, notification is comming even if topic is already solved. Good ...
2. this is interesting. I code I have generating of Waypoints name if there is non by some FI or L(X) + geocache code (third and next characters) but in cache from your mail is only "FI". Have to test it how this happen
4. finally installed GeoGet and created testing DB. Problem on my side, fixed
Hi Pavel,
yes, notification is comming even if topic is already solved. Good ...
2. this is interesting. I code I have generating of Waypoints name if there is non by some FI or L(X) + geocache code (third and next characters) but in cache from your mail is only "FI". Have to test it how this happen
4. finally installed GeoGet and created testing DB. Problem on my side, fixed
Replies have been locked on this page!