Page MenuHome

Activate transform gizmos on drag
AbandonedPublic

Authored by Campbell Barton (campbellbarton) on May 29 2019, 9:21 AM.

Diff Detail

Repository
rB Blender
Branch
TEMP-GIZMO-DRAG (branched from master)
Build Status
Buildable 3765
Build 3765: arc lint + arc unit

Event Timeline

William Reynish (billreynish) requested changes to this revision.EditedMay 29 2019, 10:37 AM

This works well for mice.

I think we should go ahead with this. It solves all issues related to selecting items obscured by gizmos.

Required change: add different thresholds for pen drag, mouse drag, keyboard drag

This revision now requires changes to proceed.May 29 2019, 10:37 AM
Brecht Van Lommel (brecht) requested changes to this revision.May 29 2019, 11:11 AM

A lower threshold for gizmos could be ok, but I have doubts about doing this everywhere. Even with a mouse 3px is quite small when selecting multiple vertices quicky.

Well, to be able to use this for gizmos, the threshold has to be quite small. 3 pixels is roughly what other apps use, and I think it’s enough for mice at least. Higher thresholds make gizmos unacceptably sluggish IMO. For still and pens we can keep a higher threshold.

I think it's fine that if you click on a gizmo it only takes a little distance to start using it.

But preferably this should not affect things like dragging things in the outliner or file browser for example, or selecting vertices when there is no gizmo in the way.

  • Separate keyboard/tablet/mouse drag thresholds

Not really a fan of making low level event click/drag detection depend on whats the cursor hovers over.

We _could_ for eg, change the drag threshold if an active gizmo exists, although this wouldn't be fool proof.

  • The gizmo might not even accept drag events (could be detected).
  • The gizmo might accept drag events but pass them through under certain conditions (we could accept this as limitation of the design).

We agreed to try the 3px for mouses, it seems ok in testing.