Select Grouped for Animation Editors #86180

Open
opened 2021-03-02 06:53:44 +01:00 by Luciano Muñoz Sessarego · 5 comments

The Select Grouped menu in the 3D view is widely used and useful, Implementing it in the animation editors would be really useful with many possible options:

Select Grouped by

  • Channel type (example if I have a key selected from X translation, it will select all the keys that are in the x translation of the visible object, if I have a key selected from x translation and y rotation, it will select all the keys that match this pattern)
  • Key Type
  • Interpolation Type
  • Modifiers (see https://developer.blender.org/T86179)

I think these are the main use cases for the select grouped function in the animation editors and it would allow for faster workflows in many cases that now just take a lots of clicks.

The Select Grouped menu in the 3D view is widely used and useful, Implementing it in the animation editors would be really useful with many possible options: Select Grouped by - Channel type *(example if I have a key selected from X translation, it will select all the keys that are in the x translation of the visible object, if I have a key selected from x translation and y rotation, it will select all the keys that match this pattern)* - Key Type - Interpolation Type - Modifiers (see https://developer.blender.org/T86179) I think these are the main use cases for the select grouped function in the animation editors and it would allow for faster workflows in many cases that now just take a lots of clicks.
Author
Member

Added subscriber: @LucianoMunoz

Added subscriber: @LucianoMunoz
Contributor

Added subscriber: @RedMser

Added subscriber: @RedMser
RedMser self-assigned this 2022-04-29 20:04:49 +02:00
Contributor

I'm interested in this feature and started working on it.

See #104758 for the PR.

I'm interested in this feature and started working on it. See #104758 for the PR.
Philipp Oeser removed the
Interest
Animation & Rigging
label 2023-02-09 14:35:52 +01:00
Contributor

Open Design Questions

  • Some modes (such as Channel Type or Modifiers) check a trait of the channel, even though it acts based on the selected keyframe.
    • Current implementation: retrieve the traits of the channel(s) of all the selected keyframes.
    • But this is very confusing if you don't have any selected keyframe, but only select a channel.
      • Idea 1: If no keyframe is selected, use the selected channel as input instead.
      • Idea 2: Only take the channel selection into account, ignore keyframe selection for these (but this may be confusing? I personally really don't like working with channel selection in Dopesheet...)
    • Also, the channels don't end up getting selected, which makes some operators like "Make Cyclic" not work correctly.
      • Idea: select a channel if all of its keyframes got selected by this operator.
  • How should the Modifiers mode work?
    • Current implementation: the same set of modifiers of a given type must be present. So Cyclic ≠ Noise ≠ Cyclic+Noise.
    • But if you want to e.g. select all cyclic channels, it's not possible if there's other modifiers too.
    • Not sure what use-cases there are, besides for cyclic.
    • Idea: A mode "Is Cyclic" might be helpful here?
  • Maybe add an "Invert" option to the operator? So select any keyframes that don't match the pattern.
    • While you can use the invert selection operator, it won't combine well with the "Extend" checkbox. Not sure if this is a common enough use-case to be worth adding.
  • There's no mode for selecting all keyframes of a channel. But I think this should be a new operator, not a mode of Select Grouped.
  • Datablock mode should probably also be split to another operator (or maybe an option of "Select All"?), it doesn't fit with the rest.
  • Grease Pencil modes.
    • Need to talk with the GP module about this, since I don't use GP at all.

Feel free to comment on any points, add suggestions, etc. :)

# Open Design Questions - [ ] Some modes (such as Channel Type or Modifiers) check a trait of the *channel*, even though it acts based on the *selected keyframe*. - Current implementation: retrieve the traits of the channel(s) of all the selected keyframes. - But this is very confusing if you don't have any selected keyframe, but only select a channel. - Idea 1: If no keyframe is selected, use the selected channel as input instead. - Idea 2: Only take the channel selection into account, ignore keyframe selection for these (but this may be confusing? I personally really don't like working with channel selection in Dopesheet...) - Also, the channels don't end up getting selected, which makes some operators like "Make Cyclic" not work correctly. - Idea: select a channel if all of its keyframes got selected by this operator. - [ ] How should the Modifiers mode work? - Current implementation: the same set of modifiers of a given type must be present. So Cyclic ≠ Noise ≠ Cyclic+Noise. - But if you want to e.g. select all cyclic channels, it's not possible if there's other modifiers too. - Not sure what use-cases there are, besides for cyclic. - Idea: A mode "Is Cyclic" might be helpful here? - [ ] Maybe add an "Invert" option to the operator? So select any keyframes that don't match the pattern. - While you can use the invert selection operator, it won't combine well with the "Extend" checkbox. Not sure if this is a common enough use-case to be worth adding. - [ ] There's no mode for selecting all keyframes of a channel. But I think this should be a new operator, not a mode of Select Grouped. - [ ] Datablock mode should probably also be split to another operator (or maybe an option of "Select All"?), it doesn't fit with the rest. - [ ] Grease Pencil modes. - Need to talk with the GP module about this, since I don't use GP at all. Feel free to comment on any points, add suggestions, etc. :)
Member

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.

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.
Alaska removed the
Status
Needs Triage
label 2024-04-07 06:09:46 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
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
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
3 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#86180
No description provided.