Touch on Gizmos can return invalid cursor coordinates #59836

Open
opened 2018-12-25 05:22:39 +01:00 by Francisco Sciaraffia · 18 comments

Blender Version
version: 2.80 (sub 39), branch: blender2.7, commit date: 2018-12-23 21:42, hash: e5e885d0ec, 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.
0.PNG

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

**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. ![0.PNG](https://archive.blender.org/developer/F6062584/0.PNG) When using a regular mouse the cursor gets hidden and it works as intended.

Added subscriber: @Evigmae

Added subscriber: @Evigmae

#68543 was marked as duplicate of this issue

#68543 was marked as duplicate of this issue

Added subscribers: @brecht, @ZedDB

Added subscribers: @brecht, @ZedDB

@brecht anyone I can assign this to?

@brecht anyone I can assign this to?

Added subscribers: @JulianEisel, @ideasman42

Added subscribers: @JulianEisel, @ideasman42

@ZedDB, possibly @ideasman42 or @JulianEisel if it's specific to gizmos.

@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?

@ZedDB, possibly @ideasman42 or @JulianEisel if it's specific to gizmos. @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.

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.

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.

Added subscriber: @PrototypeNM1

Added subscriber: @PrototypeNM1

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

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

Added subscriber: @9Laos

Added subscriber: @9Laos

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

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

Added subscriber: @seanr

Added subscriber: @seanr

I see this on a trackpad all the time (mid-2015 MacBook Pro). It's a real problem when rotating the view (sometimes it'll completely flip the view upside-down, for example) or zooming (sudden jumps in zoom distance). This when coupled with lack of proper undo for camera and view movements is worse than annoying - it can completely break a scene setup and needs to be a high priority to fix.

I see this on a trackpad all the time (mid-2015 MacBook Pro). It's a real problem when rotating the view (sometimes it'll completely flip the view upside-down, for example) or zooming (sudden jumps in zoom distance). This when coupled with lack of proper undo for camera and view movements is worse than annoying - it can completely break a scene setup and needs to be a high priority to fix.
Nicholas Rishel changed title from Touch/Pen on Gizmos can return invalid cursor coordinates to Touch on Gizmos can return invalid cursor coordinates 2020-12-28 23:01:36 +01:00

Added subscriber: @chbug

Added subscriber: @chbug

@PrototypeNM1 Hey Nicholas, I was wondering if you're still planning to work on this, as I might give it a try otherwise, as a starter project to familiarize myself with the touch/pen API.

@PrototypeNM1 Hey Nicholas, I was wondering if you're still planning to work on this, as I might give it a try otherwise, as a starter project to familiarize myself with the touch/pen API.

@chbug heads up I pm'ed you on blender.chat to follow up.

@chbug heads up I pm'ed you on blender.chat to follow up.

We chatted, and Nicholas found a better started project for me, so I won't follow up on this one.

We chatted, and Nicholas found a better started project for me, so I won't follow up on this one.
Philipp Oeser removed the
Interest
User Interface
label 2023-02-10 09:25:57 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
8 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#59836
No description provided.