Quick Map Switch: let it die!
It is a bad idea in general to have two icons that look almost the same. I recently tried to explain the concept of switching maps in Locus to a newby and it turned out to be a horrible experience: First try the quick map switch icon, then if you cant find what you`re looking for (because Locus has very strange ideas of "important" maps), you close the quick map switch window again and try your luck in the "normal" maps function. This view basically does the same thing (= switch maps), it just looks a bit different and is called by a slightly different Icon?! How non-intuitive can it get?
Shouldnt there be ONLY ONE window that switches maps? I think the (failed) "quick map switch" function could be killed off completely. Instead, in the standard maps view, you introduce a new tab: "HERE".
Leave everything else as it is (online, own, vector, wms) but in "HERE", you present a list of offline-maps available at the current screen position, sorted by scale (regardless if its vector maps or rmaps or sqlite or cached or whatever).
As for the correct sorting order for "HERE", I`d like to quote myself from a year ago:
Maps that cover my CURRENT POSITION are ALWAYS more important to me than maps that do not. Locus needs a simple list of those current maps, sorted by scale, like any other gps app or gps hardware.
I want to see
SAT5k-Matterhorn.rmap
SWISSMAP25-Zermatt.rmap
SWISSMAP50-SwitzerlandEast.rmap
KOMPASS50-Switzerland.rmap
SWISSMAP200-Switzerland.rmap
MICHELIN400-Alps.rmap
MICHELIN1000-Europe.rmap
GMAP8-World.rmap
in exactly this order on the peak of Matterhorn. I DO NOT want to see any map that does not cover my position, even if it is only ten kilometers away.
I like this idea 
As for users who prefer other "sorting" orders (like how its currently done in the quick map switch window, although i never really figured out what it does): You could simply add more TABs to the map view: For example:
HERE - CLOSE - OWN - ONLINE - VECTOR - WMS
HERE would be a sort by scale and not show anything else.
CLOSE would include the adjacent maps in some funky order.
In any case, the map view would obviously remember which TAB was open. So one could simply leave it on HERE or CLOSE and use it as a 1:1 replacement for the current quick map switch function. No additional clicks required.
As for users who prefer other "sorting" orders (like how its currently done in the quick map switch window, although i never really figured out what it does): You could simply add more TABs to the map view: For example:
HERE - CLOSE - OWN - ONLINE - VECTOR - WMS
HERE would be a sort by scale and not show anything else.
CLOSE would include the adjacent maps in some funky order.
In any case, the map view would obviously remember which TAB was open. So one could simply leave it on HERE or CLOSE and use it as a 1:1 replacement for the current quick map switch function. No additional clicks required.
There could also be a TAB called "RECENT" that will sort maps in the order they were used. Incredibly useful. So we`d have
HERE - CLOSE - RECENT - OWN - VECTOR - ONLINE - WMS
I quite like this TAB system. It is simple, it is easily understandable, it does not need any extra buttons or options, it keeps everything related to maps in one single view. Cant see a particular problem with usability either.
There could also be a TAB called "RECENT" that will sort maps in the order they were used. Incredibly useful. So we`d have
HERE - CLOSE - RECENT - OWN - VECTOR - ONLINE - WMS
I quite like this TAB system. It is simple, it is easily understandable, it does not need any extra buttons or options, it keeps everything related to maps in one single view. Cant see a particular problem with usability either.
I definitely want to keep the Quick Map Switch. I use it a lot. So. Joe, delete it from your custom tool bar first (better for your blood pressure).
And now I will study your suggestions and maybe vote!
I definitely want to keep the Quick Map Switch. I use it a lot. So. Joe, delete it from your custom tool bar first (better for your blood pressure).
And now I will study your suggestions and maybe vote!
henk, only the extra window dies, the exact same functionality would still be available with a more logical interface. why have two different places when you can just do with one?
but you are right, its better for my blood pressure to give up on UI changes. menion cannot do it anyway because every single adaption means re-translation of every text string involved. at least thats how i understood how the (horrible?) translation api in locus works :).
henk, only the extra window dies, the exact same functionality would still be available with a more logical interface. why have two different places when you can just do with one?
but you are right, its better for my blood pressure to give up on UI changes. menion cannot do it anyway because every single adaption means re-translation of every text string involved. at least thats how i understood how the (horrible?) translation api in locus works :).
stefan, you know well that it`s not about stupid translation system :). If you check your topic, you`ll see that many of them are completely or partially solved.
So I`m still working on improvements and my mind is open to changes! always ... currently is in my mind improved version of quick switch that will work in slide left panel and with better algorithm on offered maps. You solution is also interesting and have think about it, because ... why not.
stefan, you know well that it`s not about stupid translation system :). If you check your topic, you`ll see that many of them are completely or partially solved.
So I`m still working on improvements and my mind is open to changes! always ... currently is in my mind improved version of quick switch that will work in slide left panel and with better algorithm on offered maps. You solution is also interesting and have think about it, because ... why not.
Hi guys,
I also get frustrated with the "Quick Map Switch" .
In most of the cases it does not show the maps I expected. So I have to do a extra step and switch to maps. There I face the problem that I can not recognize which of my bunch of maps covers my current position....:-(
So I see 2 possible solutions:
A) enhance "Quick Map Switch" to show all offline Maps in current position at a glance. Sorted by scale.
B) Follow Joeloc`s proposal to have the maps In a HERE Tab in standard maps functionality.
Hi guys,
I also get frustrated with the "Quick Map Switch" .
In most of the cases it does not show the maps I expected. So I have to do a extra step and switch to maps. There I face the problem that I can not recognize which of my bunch of maps covers my current position....:-(
So I see 2 possible solutions:
A) enhance "Quick Map Switch" to show all offline Maps in current position at a glance. Sorted by scale.
B) Follow Joeloc`s proposal to have the maps In a HERE Tab in standard maps functionality.
The more I think about it, the more I like the TAB idea. Because basically, we always talk about "presenting a list of maps to the user". QuickMapSwitch does it and the normal map view does it as well. It would make sense to join these two and have only one location where Locus "presents lists of maps".
Also with the TABs, it would be really easy and not require any UI work to add different "views" of the map database:
HERE - Every (offline) map that covers the current screen position, sorted by scale.
NEAR - Offline maps that do not cover the current screen position, sorted by distance from current screen position to closest point in map (not to map center).
RECENT - All maps in the order they were used.
ONLINE - Just as now.
CUSTOM - Just as now.
VECTOR - Just as now.
WMS - Just as now.
... - more sorting orders, I`m sure people will come up with other useful stuff. How about e.g.
SIZE - Offline maps sorted by size on disk.
DATE - Offline maps sorted by creation date.
...
Anyway... the TAB system keeps all that stuff nicely grouped together and makes things very logical and straight forward for the user. It`s so much cleaner than yet another window (QuickMapSwitch) with a slightly different look, a slightly different toolbar button and a slightly different handling.
I think it`s easier to code as well :).
The more I think about it, the more I like the TAB idea. Because basically, we always talk about "presenting a list of maps to the user". QuickMapSwitch does it and the normal map view does it as well. It would make sense to join these two and have only one location where Locus "presents lists of maps".
Also with the TABs, it would be really easy and not require any UI work to add different "views" of the map database:
HERE - Every (offline) map that covers the current screen position, sorted by scale.
NEAR - Offline maps that do not cover the current screen position, sorted by distance from current screen position to closest point in map (not to map center).
RECENT - All maps in the order they were used.
ONLINE - Just as now.
CUSTOM - Just as now.
VECTOR - Just as now.
WMS - Just as now.
... - more sorting orders, I`m sure people will come up with other useful stuff. How about e.g.
SIZE - Offline maps sorted by size on disk.
DATE - Offline maps sorted by creation date.
...
Anyway... the TAB system keeps all that stuff nicely grouped together and makes things very logical and straight forward for the user. It`s so much cleaner than yet another window (QuickMapSwitch) with a slightly different look, a slightly different toolbar button and a slightly different handling.
I think it`s easier to code as well :).
How many tabs? Yes, I know swiping but I do not like invisible panels/tabs.
How many tabs? Yes, I know swiping but I do not like invisible panels/tabs.
I dont know how many... seven? It doesnt really matter mutch I think. Locus would obviously remember the active TAB, so I think you will be "on the right page" automatically most of the time.
Newer Android versions (since ICS?) apparently do not use this "desktop-like-tab-layout" anymore anyway. Instead, only three TABs are visible at any time, like
prevtab------------------activetab----------------nexttab
Everything elses needs to be swiped left & right. Not sure I like this much, but hey... Google pays many clever people a lot of money to make these decisions, so who are we to argue?
I know Locus likes to do things differently, ui-wise. Some stuff I like, some stuff I dont. But in the end, the best path would still be to follow the established standards and present things in a way similar to most other apps on Android. It will probably confuse long-term users for a while. But isnt it more important to NOT confuse new users instead? At least when sales are an issue, that answer should be a clear YES.
Another option if we really want all TABs visible at any given time: use icons instead of text. Eight should fit comfortably.
I dont know how many... seven? It doesnt really matter mutch I think. Locus would obviously remember the active TAB, so I think you will be "on the right page" automatically most of the time.
Newer Android versions (since ICS?) apparently do not use this "desktop-like-tab-layout" anymore anyway. Instead, only three TABs are visible at any time, like
prevtab------------------activetab----------------nexttab
Everything elses needs to be swiped left & right. Not sure I like this much, but hey... Google pays many clever people a lot of money to make these decisions, so who are we to argue?
I know Locus likes to do things differently, ui-wise. Some stuff I like, some stuff I dont. But in the end, the best path would still be to follow the established standards and present things in a way similar to most other apps on Android. It will probably confuse long-term users for a while. But isnt it more important to NOT confuse new users instead? At least when sales are an issue, that answer should be a clear YES.
Another option if we really want all TABs visible at any given time: use icons instead of text. Eight should fit comfortably.
No icons please. Interpretatation is really different sometimes for an international customer base.
Let`s have tabs then , just like we have now with a max of 4 visible and let the user choose the visible ones (just like we have now) and create some extra choices like "near" and so on (but don`t take away my right toolbar Quick map switch button).
No icons please. Interpretatation is really different sometimes for an international customer base.
Let`s have tabs then , just like we have now with a max of 4 visible and let the user choose the visible ones (just like we have now) and create some extra choices like "near" and so on (but don`t take away my right toolbar Quick map switch button).
So finally comes time to improve/destroy Quick map switch ...
my opinions
1. I have system of sliding tabs as joeloc mentioned above. This system is used in Google Play app and it`s crazy. You have no idea how much tabs you have to slide till you get at any place. It`s also slow if you want to go from one side to another
2. I don`t like idea of too much tabs. Four, used in maps is on a edge, five is limit for me
3. agree that icons are same and currently it`s complicated to see difference on first sight
4. agree that offered maps are little bit "not expected" because of used algorithm
5. who likes new left panel?
Fine, so first attempt of new "Quick map switch" http://forum.locusmap.eu/viewtopic.ph...
Sorry joeloc, I was thinking about it, and I really want to keep this useless screen, but I`m ready to make it 100% useful! Suggest to check test version I just published, so we have where to start
Warning: SQLite and GEMF maps, do not have defined bounding rectangle, so I have absolutely no idea if map is in current location available or not. Little bit problem, but that`s a way, how SQLite maps are done (GEMF maps has bbox, but it ̈s not now used by Locus). So point is, that I need to rewrite one old part to support better sorting of maps, but this will take at least another day, so in near future ...
happy testing and nice evening
So finally comes time to improve/destroy Quick map switch ...
my opinions
1. I have system of sliding tabs as joeloc mentioned above. This system is used in Google Play app and it`s crazy. You have no idea how much tabs you have to slide till you get at any place. It`s also slow if you want to go from one side to another
2. I don`t like idea of too much tabs. Four, used in maps is on a edge, five is limit for me
3. agree that icons are same and currently it`s complicated to see difference on first sight
4. agree that offered maps are little bit "not expected" because of used algorithm
5. who likes new left panel?
Fine, so first attempt of new "Quick map switch" http://forum.locusmap.eu/viewtopic.ph...
Sorry joeloc, I was thinking about it, and I really want to keep this useless screen, but I`m ready to make it 100% useful! Suggest to check test version I just published, so we have where to start
Warning: SQLite and GEMF maps, do not have defined bounding rectangle, so I have absolutely no idea if map is in current location available or not. Little bit problem, but that`s a way, how SQLite maps are done (GEMF maps has bbox, but it ̈s not now used by Locus). So point is, that I need to rewrite one old part to support better sorting of maps, but this will take at least another day, so in near future ...
happy testing and nice evening
Just take a quick look. UI seem fair. But the offered maps dont make sense. Maybe its because of sql lite but now there is mix of close and far remote maps...
Just take a quick look. UI seem fair. But the offered maps dont make sense. Maybe its because of sql lite but now there is mix of close and far remote maps...
yes I know, that`s what I wrote above in "warning" section. Task on today. Just forget on sorting of personal map. Important is usability to UI and rest /last used, most used, ...)
yes I know, that`s what I wrote above in "warning" section. Task on today. Just forget on sorting of personal map. Important is usability to UI and rest /last used, most used, ...)
Ok I will wait for next evolution step :-)
Regarding UI:
I like the left panel. It is OK.
Just detected: Cool scrolling if the list extend the current display. 1+
Also good: Filter stays at the last used value 1+
I would suppress the current map in the lists to gain more space for further maps.
For the Last Used /Nearest Maps sections : Will there be a preference about the numbers of maps to show ?
Ok I will wait for next evolution step :-)
Regarding UI:
I like the left panel. It is OK.
Just detected: Cool scrolling if the list extend the current display. 1+
Also good: Filter stays at the last used value 1+
I would suppress the current map in the lists to gain more space for further maps.
For the Last Used /Nearest Maps sections : Will there be a preference about the numbers of maps to show ?
uff, expected time, one day, on rewrite whole system for checking map, was exact ... done ;). So now all maps, SQLite, MBT, GEMF, RMap etc.. has known bounding box, so all maps should be displayed correctly when asked for nearest!
About define number. I hope this will not be necessary. I`m sure we`ll find best number of items for each section to fit needs of all
uff, expected time, one day, on rewrite whole system for checking map, was exact ... done ;). So now all maps, SQLite, MBT, GEMF, RMap etc.. has known bounding box, so all maps should be displayed correctly when asked for nearest!
About define number. I hope this will not be necessary. I`m sure we`ll find best number of items for each section to fit needs of all
I tested it with 2.9.2.5
With limited testing time, I would say:
Big improvement for the Quick Map Switch. Now it seems to get usable at all.
I tested it with 2.9.2.5
With limited testing time, I would say:
Big improvement for the Quick Map Switch. Now it seems to get usable at all.
I like the new maps offered by the enhanced quickmapswitch. Finally, it starts to make some sort of sense.
I do not like the user interface in a separate window at all, but that was to be expected.
We have two completely different "map views" which basically contain the same elements (maps) and do the same thing (switch maps). One view is somehow "linked" to the other one with a button. One view has something called "Filter" that offers more or less the same options in a popup gadget that the other view offers in a totally different way (tabs). One view is a funky "left panel" and one is a "window". All this is utterly confusing and as far away from a streamlined and pleasant UI as it can possibly get.
Dont get me wrong... I really enjoy all the powerful features that Locus offers. No other GPS app comes even close. I just think all this could easily be offered in a simpler, more standardized user interface that doesnt scare off new users immediately and requires a shitload of documentation (that nobody reads anyway). Separating "quick map switch" and "normal map switch" into two completely different things with two completely different UIs is just bad.
A similiar thing is happening with tracks. The separation into track information and track editing adds so much useless complexity all over the Locus UI it makes me cry. You could kill off one complete toolbar and about a dozen other useless buttons and menu items if this was done properly. The usability would skyrocket. But this is something for another thread...
I like the new maps offered by the enhanced quickmapswitch. Finally, it starts to make some sort of sense.
I do not like the user interface in a separate window at all, but that was to be expected.
We have two completely different "map views" which basically contain the same elements (maps) and do the same thing (switch maps). One view is somehow "linked" to the other one with a button. One view has something called "Filter" that offers more or less the same options in a popup gadget that the other view offers in a totally different way (tabs). One view is a funky "left panel" and one is a "window". All this is utterly confusing and as far away from a streamlined and pleasant UI as it can possibly get.
Dont get me wrong... I really enjoy all the powerful features that Locus offers. No other GPS app comes even close. I just think all this could easily be offered in a simpler, more standardized user interface that doesnt scare off new users immediately and requires a shitload of documentation (that nobody reads anyway). Separating "quick map switch" and "normal map switch" into two completely different things with two completely different UIs is just bad.
A similiar thing is happening with tracks. The separation into track information and track editing adds so much useless complexity all over the Locus UI it makes me cry. You could kill off one complete toolbar and about a dozen other useless buttons and menu items if this was done properly. The usability would skyrocket. But this is something for another thread...
no need for such long stories ... I`m aware of what you`re talking. I`m also sure you`re aware why I did "Quick map switch". To save you and others one or two clicks ...
Anyway suggest to check this version http://forum.locusmap.eu/viewtopic.ph... (also don`t forget to vote in above poll). Check "Online maps" tab and you`ll see
no need for such long stories ... I`m aware of what you`re talking. I`m also sure you`re aware why I did "Quick map switch". To save you and others one or two clicks ...
Anyway suggest to check this version http://forum.locusmap.eu/viewtopic.ph... (also don`t forget to vote in above poll). Check "Online maps" tab and you`ll see
Just back from a trip, maybe I have time tomorrow, but: in 2.9.2 I noticed that `automatic load of vector maps" (under menu item maps advanced) works fine but does not correct the map name in the top bar (where yo can choose Title/Map/GPS etc).
So, arriving in Italy, Locus switched to my Alps map in the scren but the topbar read "Netherlands hike".
Just a remark for future versions.
Just back from a trip, maybe I have time tomorrow, but: in 2.9.2 I noticed that `automatic load of vector maps" (under menu item maps advanced) works fine but does not correct the map name in the top bar (where yo can choose Title/Map/GPS etc).
So, arriving in Italy, Locus switched to my Alps map in the scren but the topbar read "Netherlands hike".
Just a remark for future versions.
it works, just need some time. Locus waits till is absolutely sure, that first map may be removed from memory and is not needed. Then is changed top label. It may take few seconds of using before it happen ...
btw. hope you had a nice trip ;)
it works, just need some time. Locus waits till is absolutely sure, that first map may be removed from memory and is not needed. Then is changed top label. It may take few seconds of using before it happen ...
btw. hope you had a nice trip ;)
I have GPS off and it does not change (not even after 5 minutes) unless I do some moving of the map or zooming in/out. Not a big problem.
btw Great skiing in the Dolomites. New speed record of 90.6 km/hr. I had to lower my recording interval because Locus recorded 83 km/hr.
I have GPS off and it does not change (not even after 5 minutes) unless I do some moving of the map or zooming in/out. Not a big problem.
btw Great skiing in the Dolomites. New speed record of 90.6 km/hr. I had to lower my recording interval because Locus recorded 83 km/hr.
Replies have been locked on this page!