Page MenuHome

Touch/Pen on Gizmos can return invalid cursor coordinates
Open, Confirmed, MediumPublic


Blender Version
version: 2.80 (sub 39), branch: blender2.7, commit date: 2018-12-23 21:42, hash: e5e885d0ecb9, type: Release
build date: 23/12/2018, 17:14
platform: Windows

Short description of error

When using a pen, as in a Microsoft Surface or similar device, using the camera Gizmos and moving the pen outside the 3D viewport seems to return null/invalid coordinates, and it breaks. They can ONLY be used inside the 3D viewport. It's an absolute deal breaker for touch screen users (Surface, Wacom, etc)

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).

Any default .blender. On a touch device using a stylus pen, click on a Gizmo (axis, zoom, or drag) and move the pen outside the 3D viewport.

When using a regular mouse the cursor gets hidden and it works as intended.


To Do

Event Timeline

Brecht Van Lommel (brecht) lowered the priority of this task from Normal to Needs Information from User.

@Sebastian Parborg (zeddb), possibly @Campbell Barton (campbellbarton) or @Julian Eisel (Severin) if it's specific to gizmos.

@Francisco Sciaraffia (Evigmae), do you have "Continuous Grab" enabled under "Preferences > Input"? Does the same issue happen when dragging on number buttons to change the value? When translating objects in the viewport? Or is it only an issue with these gizmos?

Yes, this is with "Continuous Grab" enabled, as it comes by default.

Translating objects also breaks when moving the pen/touch outside the 3D viewport.

But dragging number on sliders works fine.

However, disabling "Continuous Grab" does the trick as it lets you move the pen/touch outside the 3D viewport while still holding focus on the gizmo or object while returning a valid value.

This should be readily available information for artists using touch devices.

The issue is we need to detect if events are absolute, current code assumes tablet events are absolute but we don't yet detect touch input.

Bastien Montagne (mont29) raised the priority of this task from Needs Information from User to Confirmed, Medium.Mar 18 2019, 5:12 PM

When I tested gizmos with the Windows Ink API I could not reproduce for pen input with continuous grab. Touch is still broken.

Heads up that I'm working on touchscreen support which will address or obviate the touch issue.