This object is in archive!
Track multi selection delay destroys "snappy" user interface
Solved
This is not excusable from a user interface perspective: Locus MUST NOT DELAY when simply selecting/unselecting checkmarks. Not even a tenth of a second. Nor must it put up working requesters or dim the display. Nowhere. Never.
Multiselecting must always be instantaneous, no matter if the track has 30 points or 3.000 or 30.000. I dont really know whats going on here in Locus behind the scenes, but why are there such time intensive calculations required for simply selecting items in a list? I cant remember this being the case in earlier versions. Can you not revise the program logic a little and try to do those calculations elsewhere?
Files:
locus-selection...
The same problem 
I also spotted that. I think I would be better to make calculations at the end of the selecting tracks. And the progress bar ( xx / yy tracks loaded ) is a must. Users need feedback.
I also spotted that. I think I would be better to make calculations at the end of the selecting tracks. And the progress bar ( xx / yy tracks loaded ) is a must. Users need feedback.
Still happens in 2013 :/
Still happens in 2013 :/
I think it is updating the tracks database as you select the items. but such processes should really put in the "confirm dialogue" or when you press the back button instead of updating immediately, since it disturbs the user from selecting many tracks at a time.
I think it is updating the tracks database as you select the items. but such processes should really put in the "confirm dialogue" or when you press the back button instead of updating immediately, since it disturbs the user from selecting many tracks at a time.
Hmm
Hmm
Same reason here as with other "power features" I guess. People arent really supposed to use Locus for all their GIS needs. We are not meant to have hundreds of tracks with thousands of points in our databases and expect to manage them nicely. Locus is just your "on the road" extension to the "real" gps program on your "real" computer at home.
If the "viewing angle" for Locus would change from "roadside tool" to general purpose gps app, things might improve rapidly. And I think it would make total sense to change this "viewing angle". Real computers are dying out rapidly and pretty soon, the vast majority will just have a tablet at home and a smartphone on the road and thats it.
Same reason here as with other "power features" I guess. People arent really supposed to use Locus for all their GIS needs. We are not meant to have hundreds of tracks with thousands of points in our databases and expect to manage them nicely. Locus is just your "on the road" extension to the "real" gps program on your "real" computer at home.
If the "viewing angle" for Locus would change from "roadside tool" to general purpose gps app, things might improve rapidly. And I think it would make total sense to change this "viewing angle". Real computers are dying out rapidly and pretty soon, the vast majority will just have a tablet at home and a smartphone on the road and thats it.
That is true! To be honest, I don`t use any PC soft to plan my journeys. I use PC only to prepare touristic maps. The whole "navigating" is made on the go in the Locus. My problem is that I`m saving huge number of points and tracks. And Locus is getting more and more sluggish because of that :/
That is true! To be honest, I don`t use any PC soft to plan my journeys. I use PC only to prepare touristic maps. The whole "navigating" is made on the go in the Locus. My problem is that I`m saving huge number of points and tracks. And Locus is getting more and more sluggish because of that :/
no pc here either, they are such a nuisance to carry around :-). pcs are dead or will be dead soon. locus should better be prepared for that.
no pc here either, they are such a nuisance to carry around :-). pcs are dead or will be dead soon. locus should better be prepared for that.
Missing here an official statement,
Tracks are loaded in the background when they are selected - right?
I suggest to load the tracks until the end of the selection:
Selection complete -> ok -> "wait ....... loading all selected tracks"
Missing here an official statement,
Tracks are loaded in the background when they are selected - right?
I suggest to load the tracks until the end of the selection:
Selection complete -> ok -> "wait ....... loading all selected tracks"
They are loaded in foreground on main ui task. Or at least the main ui is on hold while loading happens.
My opinions are quite "extreme" on this, but I consider every single instance of a "waiting for..." or "working..." or whatever else popup window that blocks my actions to be a BUG. Of course it means more work (sometimes a lot more) for the programmer to design things nicely and snappily instead, but in the end it pays off.
As for track multi selection and displaying on map, I would even consider it "bad design" when they were loaded "in the end" in one go and Locus made me wait for this. A good design would eg just load the starting point of each track at first and show them (and the names) instantly. Then, the time consuming task of full loading happens gradually and in the background and the tracks simply appear step by step, while i can already resume using Locus normally.
They are loaded in foreground on main ui task. Or at least the main ui is on hold while loading happens.
My opinions are quite "extreme" on this, but I consider every single instance of a "waiting for..." or "working..." or whatever else popup window that blocks my actions to be a BUG. Of course it means more work (sometimes a lot more) for the programmer to design things nicely and snappily instead, but in the end it pays off.
As for track multi selection and displaying on map, I would even consider it "bad design" when they were loaded "in the end" in one go and Locus made me wait for this. A good design would eg just load the starting point of each track at first and show them (and the names) instantly. Then, the time consuming task of full loading happens gradually and in the background and the tracks simply appear step by step, while i can already resume using Locus normally.
More then two years ... well, not bad I think. Ehm, back to topic ... done.
Selection of more tracks at once by bottom "Select" button, still require loading. Anyway selecting of single track is now instant. Uff ...
More then two years ... well, not bad I think. Ehm, back to topic ... done.
Selection of more tracks at once by bottom "Select" button, still require loading. Anyway selecting of single track is now instant. Uff ...
Two years is a m a z i n g. Other requested power features are on hold way longer :)
Two years is a m a z i n g. Other requested power features are on hold way longer :)
nice!
looking forward to the new beta ;)
btw.
two years only here on UseResponse + x on Getsatisfaction.com B)
nice!
looking forward to the new beta ;)
btw.
two years only here on UseResponse + x on Getsatisfaction.com B)
Replies have been locked on this page!