This object is in archive!
Search: Keep input and unify history
Completed
Assume I'm searching for "Yukichichibu onsen" in Japan (didn't make that up ;). I first try Google, but no result. So I switch to Geonames (or search address). Argh, my input is gone - history to the rescue! I type "yu", but nothing! Both searches store different histories :(
I think it's a very common usecase to search for something in source A, and then B, and perhaps C - so it would be very helpful if the input line would be kept when changing search (as long as the dialog is open) and if all searches had the same history, don't you think?
I like this idea 
Hello Ingo,
thanks for useful idea. Agree that it make sense to keep search history same for certain services.
So for Online search, Geonames and Google Places, will be kept single history instance since next version.
Offline search works differently, new What3Words that will be added in next version as well, so only another option is points & tracks, where I think it is common use case to search separately without need to keep history united.
Thanks.
Hello Ingo,
thanks for useful idea. Agree that it make sense to keep search history same for certain services.
So for Online search, Geonames and Google Places, will be kept single history instance since next version.
Offline search works differently, new What3Words that will be added in next version as well, so only another option is points & tracks, where I think it is common use case to search separately without need to keep history united.
Thanks.
Great, always happy when a (small) good idea gets implemented so fast! :) Not many app developers who are so "can do" ;)
Great, always happy when a (small) good idea gets implemented so fast! :) Not many app developers who are so "can do" ;)
Works fine in 3.21, just one more thing: Do you think it would also be possible to keep the current input when switching search provider? Of course not, when switching to one without input field like Wiki, but e.g. when switching from Google to Geonames.
Works fine in 3.21, just one more thing: Do you think it would also be possible to keep the current input when switching search provider? Of course not, when switching to one without input field like Wiki, but e.g. when switching from Google to Geonames.
Glad it works, prefect.
About "united input" for search boxes, I'll try to look at it ...
Glad it works, prefect.
About "united input" for search boxes, I'll try to look at it ...
How about unifying the whole search mess and use proper Android searchproviders instead of customized thingies?
The whole idea of searching is that I do NOT know where to find something. Forcing me to do five different searches in six databases is horrible... really.
Eg when I search for "gibson hut", I want to find possible waypoints in my database, possible tracks in my database, possible PDFs on my phone with gibson tour descriptions, possible pictures on my phone with gibson in exif, and godknowswhatelse. And i DO NOT want to run five different searches for this... yuck... JUST ONE.
Every app that refuses to support standard android searching and thinks a customized approach is better... just adds to the mess. Locus is unfortunately no exception :(.
How about unifying the whole search mess and use proper Android searchproviders instead of customized thingies?
The whole idea of searching is that I do NOT know where to find something. Forcing me to do five different searches in six databases is horrible... really.
Eg when I search for "gibson hut", I want to find possible waypoints in my database, possible tracks in my database, possible PDFs on my phone with gibson tour descriptions, possible pictures on my phone with gibson in exif, and godknowswhatelse. And i DO NOT want to run five different searches for this... yuck... JUST ONE.
Every app that refuses to support standard android searching and thinks a customized approach is better... just adds to the mess. Locus is unfortunately no exception :(.
Replies have been locked on this page!