List "Destination - Recently used" always empty
In Progress
The list "Destination - Recently used" is always empty. It doesn't matter which kind of destination I had chosen before. I get always the information "Nothing here yet - Select a new location first". You can take s look at the screenshot.
Files:
Screenshot_2023...
Hi Uwe,
thank you for your report. We are not able to simulate your problem. At first, could you please send us file get_location_recently_used.lb located in <your-locus-directory>/data/config? Make sure you had chosen some destinations before. Thank you in advance!
Hi Uwe,
thank you for your report. We are not able to simulate your problem. At first, could you please send us file get_location_recently_used.lb located in <your-locus-directory>/data/config? Make sure you had chosen some destinations before. Thank you in advance!
It is important to know what kind of "last destinations" are stored in the list of the navigation feature.
After a bit experimenting, I found some aspects...
what is stored in last destinations:
- coordinates that are selected from the map
- result of a projection (coordinates)
not stored in the list:
- destinations chosen from POI (no matter if selected from map or from points management or from selfdefined quickdestinations)
- destination chosen from "middle of the map"
- destinations created by "search" in the destination selection
This listing of usecases is not complete, but it shows that it depends on the usecase if a last destination will get into the list or not.
In regards of user expectations, I would guess, the behaviour is a bug, because user don't think about which usecases should be in the list. They probably expect all destinations in the list, regardless which usecase it was at selection of the destination.
Suggestion: Put all recently selected destinations in the recently used list.
It is important to know what kind of "last destinations" are stored in the list of the navigation feature.
After a bit experimenting, I found some aspects...
what is stored in last destinations:
- coordinates that are selected from the map
- result of a projection (coordinates)
not stored in the list:
- destinations chosen from POI (no matter if selected from map or from points management or from selfdefined quickdestinations)
- destination chosen from "middle of the map"
- destinations created by "search" in the destination selection
This listing of usecases is not complete, but it shows that it depends on the usecase if a last destination will get into the list or not.
In regards of user expectations, I would guess, the behaviour is a bug, because user don't think about which usecases should be in the list. They probably expect all destinations in the list, regardless which usecase it was at selection of the destination.
Suggestion: Put all recently selected destinations in the recently used list.
Replies have been locked on this page!