You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When moving or rotating ways or multiselections, iD currently relies on the position of the hovered mouse cursor. This makes these operations impossible on touchscreens where pointers cannot hover—dragged touches simply pan the map.
We should look into a workflow where the mapper can grab the feature and drag it around instead of it following the cursor immediately. See also #3372 for talk of a "transform tool"…
The text was updated successfully, but these errors were encountered:
I'd like to try enabling click/tap-and-drag to move selected features without entering a special transform mode. It's simple, intuitive, and consistent with other graphics editors.
Dragging unselected features would not be supported since otherwise it would be difficult to navigate the map in dense areas without accidentally dragging something. The existing limits would remain in place, so moving large or incomplete features would still be disabled. The M hotkey could also remain and work identically, but we'd no longer need the Move button in the edit menu.
A similar solution for Rotate would be nice but more difficult.
As much as I'd love to get this done for 2.18.0 and tote "full tablet support", this will definitely take some time to get right and the release has already been delayed long enough. We can just hide the move/rotate menu buttons on touch interactions for now and tote "nearly full tablet support". Full move/rotate touch support can come in 2.18.1 or whatnot. After all, "nearly full" is better than "nearly none", which is what we have now in 2.17.3.
When moving or rotating ways or multiselections, iD currently relies on the position of the hovered mouse cursor. This makes these operations impossible on touchscreens where pointers cannot hover—dragged touches simply pan the map.
We should look into a workflow where the mapper can grab the feature and drag it around instead of it following the cursor immediately. See also #3372 for talk of a "transform tool"…
The text was updated successfully, but these errors were encountered: