Click/drag threshold forgets what was initially clicked on to drag

[Christopher M. Rogers]

In edit > preferences > Input/Output > Input Devices the Click/Drag Threshold is used to prevent accidentally moving an object during a selection action. However, Inkscape seems to also delay selecting the object until the click/drag threshold is reached. This means that if you have two overlapping objects and click and drag from the edge of one over the other, the second object gets selected instead of the one which was first clicked on.

To reproduce easily:
1. edit > preferences > Input/Output > Input Devices the Click/Drag Threshold = 20
2. draw two overlapping rectangles
3. start dragging less than 20px away from the edge of one onto the other rectangle.

Result: instead of activating the drag of the object which was clicked, it begins dragging the object which the cursor was over when it hits the 20px Click/Drag threshold.

Apart from being a bit annoying, it has some other unfortunate side effects:

1.When using the spacebar to clone an object in place, sometimes the default 4px distance is enough for the cursor to grab something nearby the duplicated object rather than the duplicate itself. The result is that the object is duplicated, but Inkscape selects and moves a different object rather than pulling along the duplicate, as it should. This happens a lot with text and other thin objects.
2. As mentioned before, sometimes the object clicked on to drag is not the object that is dragged. This is especially terrible in combination with Bug 1781898 : https://bugs.launchpad.net/inkscape/+bug/1781898

To fix: Inkscape should remember what object was clicked on initially, rather than waiting to choose it after the cursor has been moved 4px.

Additional: I also recommend that the click/drag threshold be set to 2px by default instead of 4px, as this seems to be enough to prevent errors from pen input devices (tested on Wacom tablet).

Inkscape ver:
0.92.0+devel+201807081751~ubuntu18.04.1

[LucaDC (lucadc)]

Already reported in Bug #1558942.

[Christopher M. Rogers (cajhne)]

In #1558942, the report says the problem exists when "grab sensitivity is 0", which I assume means click/drag threshold is set to 0. I can't replicate that, so I don't think it's the same bug. In this bug the grab sensitivity value does indeed affect which object is grabbed (and it shouldn't). I recommend continuing with this bug, since it's for the most recent version of Inkscape, and may also solve the previous problem.

[Christopher M. Rogers (cajhne)]

Ah, actually, grab sensitivity is a different value.

Yes, seems like the same problem. If you want to mark this bug as a duplicate, I'll point to the previous bug.

Thanks.

[Christopher M. Rogers (cajhne)]

Bug #1558942 is a duplicate of #1066474
I'll link to #1066474 in the 1.0 bugfix list.
Thanks again, LucaDC!

[grey tomorrow (gtomorrow)]

Closing because INVALID: Duplicate issue.

Please see https://gitlab.com/inkscape/inbox/-/issues/2120

If you feel this issue has been injustly closed, please feel free to open a new issue at http://inkscape.org/report . Thank you.

Closed by: https://gitlab.com/greytomorrow