Changed behavior of transform operator #99124

Closed
opened 2022-06-24 08:57:58 +02:00 by ZYC · 29 comments

System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15

Blender Version
Broken: version: 3.2.1 Release Candidate, branch: master, commit date: 2022-06-22 11:55, hash: c5c384d6ea
Worked: version: 3.1.2

Short description of error
Changed behavior of transform operator with 'g' key when using tablet.

Exact steps for others to reproduce the error

  • Use 'cursor' tool from tool bar.
  • Select a cube object.
  • Point down pen to tablet but don't move the pen.
  • Press 'g'.
  • Move pen while pen touching tablet.
  • Lift pen up to confirm the transform.

What should happen

  • The cube object transformed while pen touching tablet, confirmed while pen lift from tablet.

What happens

  • Transform operator not activated after pressing 'g'.

Additional notes

  • Switch to 'move' tool could do the same transform but that's much slower than pressing 'g' without changing tools.
  • If we press 'g' before the pen touching tablet, we enter the transform operator, but we have to transform object while pen hovering above the tablet which is very bad for controlling the transform.
  • The desired behavior is to transform while pen touching tablet then confirmed while pen lift.
    3.1 Good 3.2 Bad
    GOOD_3_1_H.264.mp4 BAD_3_2_H.264.mp4
**System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15 **Blender Version** Broken: version: 3.2.1 Release Candidate, branch: master, commit date: 2022-06-22 11:55, hash: `c5c384d6ea` Worked: version: 3.1.2 **Short description of error** Changed behavior of transform operator with 'g' key when using tablet. **Exact steps for others to reproduce the error** - Use 'cursor' tool from tool bar. - Select a cube object. - Point down pen to tablet but don't move the pen. - Press 'g'. - Move pen while pen touching tablet. - Lift pen up to confirm the transform. **What should happen** - The cube object transformed while pen touching tablet, confirmed while pen lift from tablet. **What happens** - Transform operator not activated after pressing 'g'. **Additional notes** - Switch to 'move' tool could do the same transform but that's much slower than pressing 'g' without changing tools. - If we press 'g' before the pen touching tablet, we enter the transform operator, but we have to transform object while pen hovering above the tablet which is very bad for controlling the transform. - The desired behavior is to transform while pen touching tablet then confirmed while pen lift. | 3.1 Good | 3.2 Bad | | -- | -- | | [GOOD_3_1_H.264.mp4](https://archive.blender.org/developer/F13224412/GOOD_3_1_H.264.mp4) | [BAD_3_2_H.264.mp4](https://archive.blender.org/developer/F13224409/BAD_3_2_H.264.mp4) |
Author

Added subscriber: @fatboyzzfatboyzz

Added subscriber: @fatboyzzfatboyzz
Member

Added subscriber: @OmarEmaraDev

Added subscriber: @OmarEmaraDev
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

I don't think this behavior is unexpected. Once you press the pen on the tablet, you are activating the selected tool, which is the cursor tool in this case, any keys pressed after that are handled by that active tool until it is confirmed.
To confirm, are you saying that this was different in 3.1? Because I can't replicate that myself.

I don't think this behavior is unexpected. Once you press the pen on the tablet, you are activating the selected tool, which is the cursor tool in this case, any keys pressed after that are handled by that active tool until it is confirmed. To confirm, are you saying that this was different in 3.1? Because I can't replicate that myself.
Author

Hi, this behavior is in 3.2. In 3.1 it works fine.
I use this operation to transform object or vertices while pen touching tablet with direct shortcut since roughly 2.8.
But now in 3.2 I have to first switch to one of "Move" "Rotate" "Scale" "Transform" tool instead of keep using the Cursor tool unchanged.
Here are two disadvantages when changing tools.

  • The transform gizmo showup, which I never used. I already know exactly which transform I want since I pressed the shortcut. I know I can close the display of gizmo. But I may have to open it again for other advanced tools.
  • Change tool will change state which is bad. For example you have "Move" tool activated. Now you move object by default but if you press 'g' first you got a result of 'gg' which is slide operator. But all I want is 'g' to move, 'r' to rotate etc. But now I have to remember which tool is currently selected.
    This is one simple extra step but since I transform a lot. I want the old behavior back.
Hi, this behavior is in 3.2. In 3.1 it works fine. I use this operation to **transform object or vertices while pen touching tablet with direct shortcut** since roughly 2.8. But now in 3.2 I have to first switch to one of "Move" "Rotate" "Scale" "Transform" tool instead of keep using the Cursor tool unchanged. Here are two disadvantages when changing tools. - The transform gizmo showup, which I never used. I already know exactly which transform I want since I pressed the shortcut. I know I can close the display of gizmo. But I may have to open it again for other advanced tools. - Change tool will change state which is bad. For example you have "Move" tool activated. Now you move object by default but if you press 'g' first you got a result of 'gg' which is slide operator. But all I want is 'g' to move, 'r' to rotate etc. But now I have to remember which tool is currently selected. This is one simple extra step but since I transform a lot. I want the old behavior back.
Member

I still can't replicate that on 3.1 for some reason. Do it still work with a factory reset? File > Defaults > Load Factory Settings.

I still can't replicate that on 3.1 for some reason. Do it still work with a factory reset? File > Defaults > Load Factory Settings.
Author

Broken in 3.2 so replicate in 3.2.
In 3.1 everything works.

Broken in 3.2 so replicate in 3.2. In 3.1 everything works.
Member

I understand, I am try to replicate the good behavior, not the bad. Does the good behavior happen in 3.1 with factory settings in your end?

I understand, I am try to replicate the good behavior, not the bad. Does the good behavior happen in 3.1 with factory settings in your end?
Author
  • 3.1 with factory settings. Good.
  • 3.2 with factory settings. Bad.
- 3.1 with factory settings. Good. - 3.2 with factory settings. Bad.
Member

Changed status from 'Needs User Info' to: 'Needs Triage'

Changed status from 'Needs User Info' to: 'Needs Triage'
Member

Okay. I will leave this to someone on a similar platform to triage.

Okay. I will leave this to someone on a similar platform to triage.
Author
3.1 Good [GOOD_3_1_H.264.mp4](https://archive.blender.org/developer/F13224412/GOOD_3_1_H.264.mp4) 3.2 Bad [BAD_3_2_H.264.mp4](https://archive.blender.org/developer/F13224409/BAD_3_2_H.264.mp4)

Added subscribers: @PrototypeNM1, @iss

Added subscribers: @PrototypeNM1, @iss

Don't have tablet to check, @PrototypeNM1 can you repro?

Don't have tablet to check, @PrototypeNM1 can you repro?

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

Can't reproduce. There were some changes to Wintab button input handling but I don't think they could by themselves cause this behavior.

@fatboyzzfatboyzz Can you run 3.2 from command line with the argument blender.exe --debug-wintab, recreate the bug, and copy the command line output here, and link the resulting paste to this report?

Also, can you check that your Tablet Preferences utility app isn't set up for custom mouse input in Blender 3.2?

Can't reproduce. There were some changes to Wintab button input handling but I don't think they could by themselves cause this behavior. @fatboyzzfatboyzz Can you run 3.2 from command line with the argument `blender.exe --debug-wintab`, recreate the bug, and copy the command line output [here](https://developer.blender.org/paste/edit/form/default/), and link the resulting paste to this report? Also, can you check that your Tablet Preferences utility app isn't set up for custom mouse input in Blender 3.2?
Author

blender-321--debug-wintab-output.mp4

blender-321--debug-wintab-output.txt

I have all software using the same tablet settings.
I am using WACOM CTL-672.

[blender-321--debug-wintab-output.mp4](https://archive.blender.org/developer/F13247357/blender-321--debug-wintab-output.mp4) [blender-321--debug-wintab-output.txt](https://archive.blender.org/developer/F13247361/blender-321--debug-wintab-output.txt) I have all software using the same tablet settings. I am using WACOM CTL-672.
Author

Hi @PrototypeNM1 . I have some ideas about this bug.
To start the transform operation normally in blender 3.1. I have to do the following input.

  • Cursor tool.
  • Pen touches on Tablet.
  • Press 'g' while not moving the pen.
  • Move the pen to transform.

If I move the pen before pressing 'g'. Transform operation won't start.
Maybe you developers created a new tablet input system which increased the accuracy of tablet input.
So I am not able to press 'g' while not moving the pen.

At last I want to claim that what I need is Transform object while pen touching tablet with Cursor Tool and shortcut 'g'.

Hi @PrototypeNM1 . I have some ideas about this bug. To start the transform operation normally in blender 3.1. I have to do the following input. - Cursor tool. - Pen touches on Tablet. - Press 'g' while **not moving the pen**. - Move the pen to transform. If I move the pen before pressing 'g'. Transform operation won't start. Maybe you developers created a new tablet input system which increased the accuracy of tablet input. So I am not able to press 'g' while **not moving the pen**. At last I want to claim that what I need is **Transform object while pen touching tablet with Cursor Tool and shortcut 'g'**.
Nicholas Rishel changed title from Changed behavior of transform operator with tablet to Changed behavior of transform operator 2022-07-02 17:49:03 +02:00

I get it now. This change in behavior is actually unrelated to tablets, you can see the same change in behavior from Blender 3.1 to 3.2 with a mouse.

I get it now. This change in behavior is actually unrelated to tablets, you can see the same change in behavior from Blender 3.1 to 3.2 with a mouse.

Changed status from 'Needs User Info' to: 'Confirmed'

Changed status from 'Needs User Info' to: 'Confirmed'

@OmarEmaraDev I don't think this is a platform issue, since this isn't just a tablet problem and afaik mouse input handling hasn't changed for Windows recently. More likely the transform operator was subtly changed.

Edit: Was the 3D cursor previously transformable?

@OmarEmaraDev I don't think this is a platform issue, since this isn't just a tablet problem and afaik mouse input handling hasn't changed for Windows recently. More likely the transform operator was subtly changed. Edit: Was the 3D cursor previously transformable?

I am not familiar with tablets, I assumed that only applying certain pressure would register as left click. Not sure if this would be considered as a bug, personally I wouldn't expect to be able to run operator after clicking with tool chosen.

I am not familiar with tablets, I assumed that only applying certain pressure would register as left click. Not sure if this would be considered as a bug, personally I wouldn't expect to be able to run operator after clicking with tool chosen.
Member

Added subscribers: @ideasman42, @JulienKaspar

Added subscribers: @ideasman42, @JulienKaspar
Member

This behaviour change in 3,2 is actually due to an improvement to click & dragging that I've discussed with @campbellbarton.
What is happening is that while holding a click, and pressing a shortcut, Blender will immediately execute the operation that would've happened on a click & drag and use the shortcut for that operation.
This made any click & drag operation from using active tools faster and less error prone, because you can already use modal shortcuts of the active tool in between the click and reaching the drag threshold.
So pressing a shortcut no longer results in the wrong operation being applied (or in some cases the operation never getting executed).
So in that case this is not a bug but the intended behaviour.

In the example shown with the 3D cursor, it's correctly executing the cursor tool when click & holding and then pressing G, R or S. Afterwards it is immediately using that shortcut for the modal operation that would've been executed when reaching the drag threshold.

@fatboyzzfatboyzz What I'd like to know is why you are already click and holding with the left mouse button / pen and then pressing G? Why not just press G?
This might just be a workflow issue.

This behaviour change in 3,2 is actually due to an improvement to click & dragging that I've discussed with @campbellbarton. What is happening is that while holding a click, and pressing a shortcut, Blender will immediately execute the operation that would've happened on a click & drag and use the shortcut for that operation. This made any click & drag operation from using active tools faster and less error prone, because you can already use modal shortcuts of the active tool in between the click and reaching the drag threshold. So pressing a shortcut no longer results in the wrong operation being applied (or in some cases the operation never getting executed). So in that case this is not a bug but the intended behaviour. In the example shown with the 3D cursor, it's correctly executing the cursor tool when click & holding and then pressing G, R or S. Afterwards it is immediately using that shortcut for the modal operation that would've been executed when reaching the drag threshold. @fatboyzzfatboyzz What I'd like to know is why you are already click and holding with the left mouse button / pen and then pressing `G`? Why not just press `G`? This might just be a workflow issue.
Author

@JulienKaspar About why not just press G.
If we press 'g' before the pen touching tablet, we enter the transform operator, but we have to transform object while pen hovering above the tablet which is very bad for controlling the transform.
I want the transform happens while my pen touching the tablet for precise control.

If I switch to one of "Move" "Rotate" "Scale" "Transform" tool I am able to transform while pen touching tablet but there are two disadvantages when changing tools.

  • The transform gizmo showup, which I never used. I already know exactly which transform I want since I pressed the shortcut. I know I can close the display of gizmo. But I may have to open it again for other advanced tools.
  • Change tool will change state which is bad. For example you have "Move" tool activated. Now you move object by default but if you press 'g' first you got a result of 'gg' which is slide operator. All I want is 'g' to move, 'r' to rotate etc but now I have to remember which tool is currently selected.

Use the transform gizmo also let me transform while pen touching tablet but this requires me hovering the pen and move the mouse cursor to gizmo first. Much slower than just clicking anywhere press 'g' and do the precise transform.

@JulienKaspar About why not just press G. If we press 'g' before the pen touching tablet, we enter the transform operator, but we have to transform object while pen hovering above the tablet which is very bad for controlling the transform. **I want the transform happens while my pen touching the tablet for precise control.** If I switch to one of "Move" "Rotate" "Scale" "Transform" tool I am able to transform while pen touching tablet but there are two disadvantages when changing tools. - The transform gizmo showup, which I never used. I already know exactly which transform I want since I pressed the shortcut. I know I can close the display of gizmo. But I may have to open it again for other advanced tools. - Change tool will change state which is bad. For example you have "Move" tool activated. Now you move object by default but if you press 'g' first you got a result of 'gg' which is slide operator. All I want is 'g' to move, 'r' to rotate etc but now I have to remember which tool is currently selected. Use the transform gizmo also let me transform while pen touching tablet but this requires me hovering the pen and move the mouse cursor to gizmo first. Much slower than just clicking anywhere press 'g' and do the precise transform.

Removed subscriber: @PrototypeNM1

Removed subscriber: @PrototypeNM1
Member

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'
Member

@fatboyzzfatboyzz This is not how the operators are meant to be used though. This behaviour was only possible for the transform operators before, not any of the other modal operator shortcuts.
But you are free to customise the keymap to your liking. You can change the shortcuts to a "Left Mouse Press" with the G key as a modifier key. Then enable "Confirm on release" in the operator settings of the keymap entry.

@fatboyzzfatboyzz This is not how the operators are meant to be used though. This behaviour was only possible for the transform operators before, not any of the other modal operator shortcuts. But you are free to customise the keymap to your liking. You can change the shortcuts to a "Left Mouse Press" with the `G` key as a modifier key. Then enable "Confirm on release" in the operator settings of the keymap entry.
Author

@JulienKaspar
Setting 'g' as modifier key requires first hold the 'g' key then use pen touch the tablet.
Feels weird when the holding key is not 'Ctrl' or 'Shift' like key anyway.

Also I found the select box tool does exactly what I want which do not require any changed settings.
Maybe this behavior is a bug since left click with select box tool did not start box selecting.
Please don't change this select box tool behavior in future.

@JulienKaspar Setting 'g' as modifier key requires first hold the 'g' key then use pen touch the tablet. Feels weird when the holding key is not 'Ctrl' or 'Shift' like key anyway. Also I found the select box tool does exactly what I want which do not require any changed settings. Maybe this behavior is a bug since left click with select box tool did not start box selecting. Please don't change this select box tool behavior in future.
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
5 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#99124
No description provided.