Curves Interactions in the Graph Editor #84901
Labels
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#84901
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Curves manipulation in the graph editor
The aim of this design task is to write everything related to the changes that should be added in the graph editor regarding curves selection and manipulation. The functionalities described here are only some initial ideas that need to be debated.
Goal: to allow the users to manipulate keyframes more easily by the use of the computed curves themselves.
The actions performed through curves are nothing but quicker and more efficient ways to accomplish actions on the curves' keyframes.
Box selection (box, lasso, circle):
(I'm less sure about the usefulness of these twos:)
Click selection:
Added subscribers: @troopy28, @dr.sybren, @LucianoMunoz
I agree with this, I think it's what we've been looking for in terms of handling the curves:
Though the "ALT" ones I don't think we want to implement just yet as the visibility functionality needs a major overhaul too to become fast and intuitive.
Added subscriber: @kvick
Please add this, would be very much appreciated!
Added subscriber: @AdamEarle
Looking at this as an animator and coming from Maya I always thought the current keymap was good and very tidy.
Shift Selection of the curves is a good idea.
It would be good to get a side-by-side comparison of what it is now and the potential changes. This should help things to become more relevant and also help group ideas to together into the commonly performed task.
Re-reading and tinkering with Blender to find a current already available way for box-selecting curves, I can now see how this would be super handy.
Personally I nearly never use box select I am a Lassoo kinda guy.
If box selecting was to be supported than I would also say support every other method for selecting curves. Best to keep things consistent.
All area-based selection tools (including circle and lasso) should already work. They were added in D11181.
I noticed some people filed bug reports about inconsistencies in the selection behaviour though. Maybe this should be discussed sometime in a future meeting?
Added subscriber: @L0Lock
Let me know if this isn't the right place for this:
Could there be an option so that channel selection automatically isolates the curves display?
It could be a simple checkbox in the view menu, like (sync channel selection to visibility). It would make it way more efficient to manage curves visibility, and it feels more inline with how animation editors only display selected elements' keys by default.
Likewise, it could also be used in the dope sheet.
This task is specifically for the curve selection behaviour. For other features (I believe managing visibility is a separate feature from managing selection), it is probably better to create a separate task, or come to a meeting and propose your ideas.
Until then, the current way to manage visibility easily is to select the curves you are interested in and press shift+H (hide non-selected curves).
That's an interesting idea
3D space has local mode right by pressing the "Question mark" key. Perhaps the same could be done with the curves instead of the above suggestion
Glad you find it interesting, but adding a local mode to curves is barely different from the current
Shift
H
. And very different from the idea of "display only selected channel's curves".Yeah, I had a doubt, the curve "interaction" and "manipulation" in the title and preamble seemed to encapsulate curve display to me, but the rest of the post only talked about selection, so I wasn't sure. Another topic then.
Just to be sure, can anyone make such new tasks like this, or should this be reserved to developers only?
@AdamEarle @L0Lock Please keep things on topic here. @troopy28 already indicated that this is off-topic; this is not a public discussion forum but a tracker for Blender development with a very specific purpose.
This is reserved for module members. This is not a place where you can post feature requests. It's probably best to create a design for this on Right-Click Select (or help to improve one if there is already something about this topic, which I think there will be), then once the design is solidified, present it at a module meeting.
I am removing the
Needs Triage
label. This is under the general rule that Design and TODO tasks should not have a status.If you believe this task is no longer relevant, feel free to close it.