Graph editor selects keyframe on click down instead of click up and makes curve selection unexpectedly clunky #115448

Open
opened 2023-11-26 18:27:35 +01:00 by Loïc DAUTRY · 6 comments

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 531.79

Blender Version
Broken: version: 4.0.0, branch: blender-v4.0-release, commit date: 2023-11-13 17:26, hash: 878f71061b8e
Worked: seems to have always been the case?

Short description of error
Unlike in the 3D viewport, where selection happens on releasing the mouse button, selection in the graph happens on pressing down the button.

The problem is, if your goal is to select the curve via box selection but you click near a keyframe, the keyframe will be selected instead and start moving when you move your mouse thinking to do a box select.
The user can just go select from further away, but sometimes you have multiple curves and keys in a tight space so you really need to "get out of the current space", and either way it's a minor inconvenience that does get you out of your flow.

You can test it on this mock scene:
untitled.blend

**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 531.79 **Blender Version** Broken: version: 4.0.0, branch: blender-v4.0-release, commit date: 2023-11-13 17:26, hash: `878f71061b8e` Worked: seems to have always been the case? **Short description of error** Unlike in the 3D viewport, where selection happens on releasing the mouse button, selection in the graph happens on pressing down the button. The problem is, if your goal is to select the curve via box selection but you click near a keyframe, the keyframe will be selected instead and start moving when you move your mouse thinking to do a box select. The user can just go select from further away, but sometimes you have multiple curves and keys in a tight space so you really need to "get out of the current space", and either way it's a minor inconvenience that does get you out of your flow. You can test it on this mock scene: [untitled.blend](/attachments/01cc9c55-47e0-4738-a3f2-8e0f828df4eb)
Loïc DAUTRY added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-11-26 18:27:36 +01:00
Member

Hi, thanks for the report. I can confirm. This is true for other animation editors as well so I would guess this as intentional workflow.
Forwarding to A&R module devs for further decision.

Hi, thanks for the report. I can confirm. This is true for other animation editors as well so I would guess this as intentional workflow. Forwarding to A&R module devs for further decision.
Member

Following diff will allow to invoke box select instead of select and tweak behavior for graph editor. This might be good for consistency but I don't know how animators wanted this.
cc @ChrisLend

diff --git a/scripts/presets/keyconfig/keymap_data/blender_default.py b/scripts/presets/keyconfig/keymap_data/blender_default.py
index 8271499c6d9..046c144a5ed 100644
--- a/scripts/presets/keyconfig/keymap_data/blender_default.py
+++ b/scripts/presets/keyconfig/keymap_data/blender_default.py
@@ -1830,7 +1830,7 @@ def km_graph_editor(params):
     items.extend([
         ("wm.context_toggle", {"type": 'H', "value": 'PRESS', "ctrl": True},
          {"properties": [("data_path", 'space_data.show_handles')]}),
-        ("graph.clickselect", {"type": params.select_mouse, "value": 'PRESS'},
+        ("graph.clickselect", {"type": params.select_mouse, "value": 'RELEASE'},
          {"properties": [("deselect_all", not params.legacy)]}),
         ("graph.clickselect", {"type": params.select_mouse, "value": 'PRESS', "alt": True},
          {"properties": [("column", True)]}),
@@ -1857,7 +1857,7 @@ def km_graph_editor(params):
         ("graph.select_box", {"type": 'B', "value": 'PRESS', "alt": True},
          {"properties": [("axis_range", True)]}),
         ("graph.select_box", {"type": params.select_mouse, "value": 'CLICK_DRAG'},
-         {"properties": [("tweak", True), ("mode", 'SET')]}),
+         {"properties": [("tweak", False), ("mode", 'SET')]}),
         ("graph.select_box", {"type": params.select_mouse, "value": 'CLICK_DRAG', "shift": True},
          {"properties": [("tweak", True), ("mode", 'ADD')]}),
         ("graph.select_box", {"type": params.select_mouse, "value": 'CLICK_DRAG', "ctrl": True},

@L0Lock , you can tweak the keymap yourself to achieve the behavior you wanted (Edit > preferences > keymap).

Following diff will allow to invoke box select instead of `select and tweak` behavior for graph editor. This might be good for consistency but I don't know how animators wanted this. cc @ChrisLend ``` diff --git a/scripts/presets/keyconfig/keymap_data/blender_default.py b/scripts/presets/keyconfig/keymap_data/blender_default.py index 8271499c6d9..046c144a5ed 100644 --- a/scripts/presets/keyconfig/keymap_data/blender_default.py +++ b/scripts/presets/keyconfig/keymap_data/blender_default.py @@ -1830,7 +1830,7 @@ def km_graph_editor(params): items.extend([ ("wm.context_toggle", {"type": 'H', "value": 'PRESS', "ctrl": True}, {"properties": [("data_path", 'space_data.show_handles')]}), - ("graph.clickselect", {"type": params.select_mouse, "value": 'PRESS'}, + ("graph.clickselect", {"type": params.select_mouse, "value": 'RELEASE'}, {"properties": [("deselect_all", not params.legacy)]}), ("graph.clickselect", {"type": params.select_mouse, "value": 'PRESS', "alt": True}, {"properties": [("column", True)]}), @@ -1857,7 +1857,7 @@ def km_graph_editor(params): ("graph.select_box", {"type": 'B', "value": 'PRESS', "alt": True}, {"properties": [("axis_range", True)]}), ("graph.select_box", {"type": params.select_mouse, "value": 'CLICK_DRAG'}, - {"properties": [("tweak", True), ("mode", 'SET')]}), + {"properties": [("tweak", False), ("mode", 'SET')]}), ("graph.select_box", {"type": params.select_mouse, "value": 'CLICK_DRAG', "shift": True}, {"properties": [("tweak", True), ("mode", 'ADD')]}), ("graph.select_box", {"type": params.select_mouse, "value": 'CLICK_DRAG', "ctrl": True}, ``` @L0Lock , you can tweak the keymap yourself to achieve the behavior you wanted (`Edit > preferences > keymap`).

that would mean that you can no longer drag keys around. I don't think we should be changing that behavior.
But I'll put it on the meeting agenda

that would mean that you can no longer drag keys around. I don't think we should be changing that behavior. But I'll put it on the meeting agenda
Member

Thanks @ChrisLend . Yes, this will break the "tweak" thing :)

Thanks @ChrisLend . Yes, this will break the "tweak" thing :)

So this was discussed in the recent A&R meeting and we decided to put this down as a known issue.
Some people rely on that behavior, so we can't just change it.
The proper way to do it (which would be consistent with the rest of blender) is to have a toolbar in the animation editors so you can choose the tweak tool or the box select tool.

So this was discussed in the recent [A&R](https://devtalk.blender.org/t/2023-11-30-animation-rigging-module-meeting/32323#patch-review-decision-time-4) meeting and we decided to put this down as a known issue. Some people rely on that behavior, so we can't just change it. The proper way to do it (which would be consistent with the rest of blender) is to have a toolbar in the animation editors so you can choose the tweak tool or the box select tool.

Unlike in the 3D viewport, where selection happens on releasing the mouse button

I just wanted to provide some historical context here. Blender has always responded on mouse-down as much as possible, as that makes the application feel more responsive. Selection in the 3D Viewport was also on mouse-down. This only changed when introducing left-click select (LCS); with right-click select it's still immediately selecting on mouse-down. LCS has to distinguish between box-select and click-select, which can only be done by inspecting the distance traveled since the mouse-down event, and thus selection can only happen on mouse-up.

> Unlike in the 3D viewport, where selection happens on releasing the mouse button I just wanted to provide some historical context here. Blender has always responded on mouse-down as much as possible, as that makes the application feel more responsive. Selection in the 3D Viewport was also on mouse-down. This only changed when introducing left-click select (LCS); with right-click select it's still immediately selecting on mouse-down. LCS has to distinguish between box-select and click-select, which can only be done by inspecting the distance traveled since the mouse-down event, and thus selection can only happen on mouse-up.
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
4 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#115448
No description provided.