This object is in archive! 
Improvement in waypoint or track list management
Completed
I would be great if Locus could remember the current position in lists of waypoints or tracks when going back to the list after some browsing of the map. When dealing with large lists (> 300), finding the current waypoint or track requires somescrolling down (when the list is sorted on a criteria different from distance).
Additional improvement could be to be able to add a filter for waypoints or tracks selected for display on the map.
Hi Kerenoc,
do you mean waypoints for geocaching or simple points in data manager? Locus is able to filter simple points based on type of point or based on name. See the link below, please.
http://docs.locusmap.eu/doku.php/manu...
You can also filter the tracks but only based on the name.
http://docs.locusmap.eu/doku.php/manu...
Are these information sufficient for you?
regards
Petr
Hi Kerenoc,
do you mean waypoints for geocaching or simple points in data manager? Locus is able to filter simple points based on type of point or based on name. See the link below, please.
http://docs.locusmap.eu/doku.php/manu...
You can also filter the tracks but only based on the name.
http://docs.locusmap.eu/doku.php/manu...
Are these information sufficient for you?
regards
Petr
Coming back to this idea. From the maps, when going to the points categories list, Locus remember where it was in the list (level of scrolling down the list). When choosing a specific category, it doesn`t remember where it was in the waypoints list.
A possible workaround could be to add a filter to display only the currently selected points.
Coming back to this idea. From the maps, when going to the points categories list, Locus remember where it was in the list (level of scrolling down the list). When choosing a specific category, it doesn`t remember where it was in the waypoints list.
A possible workaround could be to add a filter to display only the currently selected points.
this feature is already implemented since 2.16.0 version
this feature is already implemented since 2.16.0 version
Replies have been locked on this page!