Make dragging unselected POI do "select & pan" #3562
Comments
Author: bryce2[at]obviously.com See also: http://trac.openstreetmap.org/ticket/3810
|
Author: stevage I like 2. Panning is 10 (100? 1000?) times more frequent than dragging, so having the modifier for panning is just wrong. Also, having shift+drag=pan means we couldn't have selection boxes. |
Author: Richard 2 is clearly the only sane one. :) |
Author: stevage Ugh, if evidence was required that ways get dragged accidentally: http://www.openstreetmap.org/browse/way/30142120/history Just discovered this - apparently I dragged a street a few hundred metres to the west, and saved it, without even noticing. |
Author: Richard Dragging an object now requires the object to be selected first. Panning behaviour remains unchanged, i.e. you have to drag on an empty bit of map. I'll see how this pans out (pun unintended) in the medium term, and then maybe consider adding the ability to pan if you drag an unselected object, but for now I'd rather not. Thought for the day: the fix was deleting three lines and changing half a line of code (systemed/potlatch2@4003505), and took about five minutes. People have spent orders of magnitude more time filing tickets/usability reports/what-have-you about this... than actually fixing it. If only people were more prepared to roll up their sleeves and do stuff... ;) |
Author: stevage A usability issue I have noticed:
TL;DR: dragging an unselected POI should select the POI. |
Reporter: stevage
[Submitted to the original trac issue database at 2.23pm, Thursday, 3rd March 2011]
(Richard Mann, potlatch-dev 4 mar 2011)
"I don't know whether it's really a bug or not, but I do find myself
moving objects unintentionally when panning, which isn't entirely
user-friendly. I'd prefer that drag on an unselected object resulted
in select & pan."
Fwiw, I agree.
The text was updated successfully, but these errors were encountered: