Ticket #3562 (reopened enhancement)

Opened 3 years ago

Last modified 3 years ago

Make dragging unselected POI do "select & pan"

Reported by: stevage Owned by: potlatch-dev@…
Priority: minor Milestone:
Component: potlatch2 Version:
Keywords: Cc:

Description

(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.

Change History

comment:1 Changed 3 years ago by bryce2@…

See also:  http://trac.openstreetmap.org/ticket/3810 I also find myself moving objects unintentionally. And even more often wondering if I just did move something or not (but afraid to press undo because it might undo a real change I just made).


The options here seem to be: 1) Drag unselected object moves the object. 2) Drag unselected object results in select & pan. 3) Beginners pan with arrow keys, advanced users pan with shift-drag 4) Use undocumented ActionScript? to allow advanced users to drag with the right mouse button (ala JOSM).

Personally I like option #3, even though it presents some barrier to new users understanding how to move around.

comment:2 Changed 3 years ago by 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.

comment:3 Changed 3 years ago by Richard

2 is clearly the only sane one. :)

comment:4 Changed 3 years ago by 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.

comment:5 Changed 3 years ago by Richard

  • Status changed from new to closed
  • Resolution set to fixed

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 ( https://github.com/systemed/potlatch2/commit/400350561611374b406a1bd91bb8474f2f4d070e), 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... ;)

comment:6 Changed 3 years ago by stevage

  • Status changed from closed to reopened
  • Resolution fixed deleted

A usability issue I have noticed: 1) User "drags" unselected POI 2) While mouse is over POI, it becomes selected, but as mouse moves further, it becomes unselected again 3) User releases mouse. POI is unselected, and has not moved. 4) Repeat from step 1.

TL;DR: dragging an unselected POI should select the POI.

Note: See TracTickets for help on using tickets.