blender/blender
142
451
Fork 651
Code Issues 6.5k Pull Requests 823 Projects 18 Wiki Activity

Select key in dopesheet deselect bone in the viewport (only show selected disabled) #71615

New Issue
Open
opened 2019-11-15 17:36:47 +01:00 by Cenek Strichel · 16 comments
Cenek Strichel commented 2019-11-15 17:36:47 +01:00
Copy Link

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-08 22:59, hash: 0a0d735acd
Worked: (optional)

Short description of error
If you select key in Dopesheet without Only selected, it deselect your bone in viewport

Exact steps for others to reproduce the error

  1. open deselectBone.blend
  2. select bone in Pose mode
  3. select any key in dopesheet without "Only selected"
  4. bone is now deselected in viewport
**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48 **Blender Version** Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-08 22:59, hash: `0a0d735acd` Worked: (optional) **Short description of error** If you select key in Dopesheet without Only selected, it deselect your bone in viewport **Exact steps for others to reproduce the error** 1) open [deselectBone.blend](https://archive.blender.org/developer/F8092721/deselectBone.blend) 2) select bone in Pose mode 3) select any key in dopesheet without "Only selected" 4) bone is now deselected in viewport
Cenek Strichel commented 2019-11-15 17:36:47 +01:00
Author
Copy Link

Added subscriber: @Cenda

Added subscriber: @Cenda
blender-admin commented 2019-11-15 17:36:47 +01:00
Copy Link

#99699 was marked as duplicate of this issue

#99699 was marked as duplicate of this issue
blender-admin commented 2019-11-15 17:36:47 +01:00
Copy Link

#88817 was marked as duplicate of this issue

#88817 was marked as duplicate of this issue
Philipp Oeser commented 2019-11-18 12:24:07 +01:00
Member
Copy Link

Added subscribers: @JulianEisel, @dr.sybren, @lichtwerk

Added subscribers: @JulianEisel, @dr.sybren, @lichtwerk
Philipp Oeser commented 2019-11-18 12:24:07 +01:00
Member
Copy Link

Can confirm, 2.79 behaved the same here.

CC @JulianEisel (involved in Animation Editors selection stuff)
CC @dr.sybren

Can confirm, 2.79 behaved the same here. CC @JulianEisel (involved in Animation Editors selection stuff) CC @dr.sybren
Hjalti Hjálmarsson was assigned by Sybren A. Stüvel 2020-01-02 13:48:05 +01:00
Sybren A. Stüvel commented 2020-01-02 13:48:05 +01:00
Member
Copy Link

Added subscriber: @Hjalti

Added subscriber: @Hjalti
Sybren A. Stüvel commented 2020-01-02 13:48:05 +01:00
Member
Copy Link

@Hjalti There are some rules in place for synchronising pose bone selection with the channel list selection. Do you remember which rules were intended?

@Hjalti There are some rules in place for synchronising pose bone selection with the channel list selection. Do you remember which rules were intended?
Sybren A. Stüvel commented 2020-01-06 17:01:56 +01:00
Member
Copy Link

I'm marking this as known issue. We need to look into it, but that would require a proper design. I've added this task to https://wiki.blender.org/wiki/User:Sybren/Animation_Weak_Areas#Selection_synchronisation_between_pose_bones_and_animation_channels to ensure we won't forget it.

I'm marking this as known issue. We need to look into it, but that would require a proper design. I've added this task to https://wiki.blender.org/wiki/User:Sybren/Animation_Weak_Areas#Selection_synchronisation_between_pose_bones_and_animation_channels to ensure we won't forget it.
Hjalti Hjálmarsson was unassigned by Sybren A. Stüvel 2020-11-17 15:18:35 +01:00
Pratik Borhade commented 2021-06-04 08:11:13 +02:00
Member
Copy Link

Added subscribers: @juba-yourgen, @PratikPB2123

Added subscribers: @juba-yourgen, @PratikPB2123
Cenek Strichel commented 2021-07-16 09:53:22 +02:00
Author
Copy Link

Any news with this problem? I see that it is same in the 3.0

Any news with this problem? I see that it is same in the 3.0
Pratik Borhade commented 2022-07-15 08:26:22 +02:00
Member
Copy Link

Added subscriber: @ChristiaanMoleman

Added subscriber: @ChristiaanMoleman
Christiaan Moleman commented 2022-07-15 09:26:06 +02:00
Copy Link

So, any news on this being fixed in 2022??? Since this has been a known issue since 2019 (!) and is extremely annoying for the end user and seemingly a relatively small thing to fix? Even if there isn't an elegant solution surely there must a simple fix or 'hack' that could be applied to solve this? Make an add-on if you must, just please do something about it. This is making animating in Blender way more of a hassle than it needs to be.

So, any news on this being fixed in 2022??? Since this has been a known issue since **2019** (!) and is *extremely* annoying for the end user and seemingly a relatively small thing to fix? Even if there isn't an elegant solution surely there must a simple fix or 'hack' that could be applied to solve this? Make an add-on if you must, just please do something about it. This is making animating in Blender way more of a hassle than it needs to be.
Christiaan Moleman commented 2022-07-15 12:36:56 +02:00
Copy Link

Seriously, what is there to design here? Just make selection consistent so that both single click and drag box keyframe selection do not affect selection in the viewport for bones same as they already do for regular objects.

Seriously, what is there to design here? Just make selection **consistent** so that both single click and drag box keyframe selection do not affect selection in the viewport for bones same as they already do for regular objects.
Brad Clark commented 2022-07-15 22:07:33 +02:00
Member
Copy Link

Added subscriber: @BClark

Added subscriber: @BClark
Philipp Oeser removed the
Interest
Animation & Rigging
 label 2023-02-09 14:36:17 +01:00
Philipp Oeser commented 2024-05-16 09:55:19 +02:00
Member
Copy Link

This has been reported again in #121781.

I have looked at it for a bit, here is my comment from #121781 (also asked this in chat):

atm. we have the current situation:
- selecting keys in animation editors (even if on FCurves on the same bone) clears the corresponding (bone)channelgroup selection, deselects the bone (I think we can agree that this is not desired?)
- selecting individual channels (even if on FCurves on the same bone) clears the corresponding (bone)channelgroup, deselects the bone (I think we can agree that this is not desired?)
- generally, you can select a channel from one bone (in the channels list) and select a different bone in the viewport (so channel <> (bone)channelgroup is not guaranteed to be corresponding)
- generally, you can select a key in an FCurve and select a different channel in the channel list (so key <> channel is not guaranteed to be corresponding)
- generally, bone selection in the viewport seems to always correspond to (bone)channelgroup selection (which is good)

So trying to get some sort of rule out of this:
- key selection in an FCurve should ripple up to the corrsponding channel (channel should also get selected -- this is the case now)
- channel selection should not mess with key selection (this is the case now)
- key selection should not mess with (bone)channelgroup selection (this is my proposal), alternatively: if a channel get selected (because one of its keys is selected) > also select the (bone)channelgroup it is in?
- channel selection should not mess with (bone)channelgroup selection (this is my proposal), alternatively: if a channel get selected > also select the (bone)channelgroup it is in?
- OR: if we still want to clear (bone)channelgroup selection in the above two, just dont do "real" bone deselection synced to the viewport as well? this would break the "which is good" part above though

there is also inconsistencies:
- in the Graph Editor, you can select a key from one FCurve, then SHIFT select a key from a different FCurve >> both channels get selected in the channels list
- in the Dopesheet however, you can select a key from one FCurve, then SHIFT select a key from a different FCurve >> only the first channel is selected in the channels list

Feedback welcome!
This has been reported again in #121781. I have looked at it for a bit, here is my comment from #121781 (also asked this in chat): ``` atm. we have the current situation: - selecting keys in animation editors (even if on FCurves on the same bone) clears the corresponding (bone)channelgroup selection, deselects the bone (I think we can agree that this is not desired?) - selecting individual channels (even if on FCurves on the same bone) clears the corresponding (bone)channelgroup, deselects the bone (I think we can agree that this is not desired?) - generally, you can select a channel from one bone (in the channels list) and select a different bone in the viewport (so channel <> (bone)channelgroup is not guaranteed to be corresponding) - generally, you can select a key in an FCurve and select a different channel in the channel list (so key <> channel is not guaranteed to be corresponding) - generally, bone selection in the viewport seems to always correspond to (bone)channelgroup selection (which is good) So trying to get some sort of rule out of this: - key selection in an FCurve should ripple up to the corrsponding channel (channel should also get selected -- this is the case now) - channel selection should not mess with key selection (this is the case now) - key selection should not mess with (bone)channelgroup selection (this is my proposal), alternatively: if a channel get selected (because one of its keys is selected) > also select the (bone)channelgroup it is in? - channel selection should not mess with (bone)channelgroup selection (this is my proposal), alternatively: if a channel get selected > also select the (bone)channelgroup it is in? - OR: if we still want to clear (bone)channelgroup selection in the above two, just dont do "real" bone deselection synced to the viewport as well? this would break the "which is good" part above though there is also inconsistencies: - in the Graph Editor, you can select a key from one FCurve, then SHIFT select a key from a different FCurve >> both channels get selected in the channels list - in the Dopesheet however, you can select a key from one FCurve, then SHIFT select a key from a different FCurve >> only the first channel is selected in the channels list Feedback welcome! ```
Philipp Oeser changed title from Select key in dopesheet deselect bone in the viewport to Select key in dopesheet deselect bone in the viewport (only show selected disabled) 2024-05-16 10:05:27 +02:00
Nathan Vegdahl commented 2024-05-24 12:13:56 +02:00
Member
Copy Link

We discussed this at this week's animation & rigging module meeting. We decided that we should prioritize this, start a proper design task, and finally get this taken care of.

No promises on a specific timeline, of course. But let's not let this last another five years.

Some things to note from the module meeting discussion:

  • This may impact grease pencil, as some of its workflows apparently need channel/selection syncing to be a smooth/efficient user experience.
  • The reported behavior happens with bone selection in pose mode, but not with objects in object mode. So this is yet another weird case where animation features behave differently with bones than they do with objects. Whatever the design ends up being, it should be consistent between objects and bones.
We discussed this at [this week's animation & rigging module meeting](https://devtalk.blender.org/t/2024-05-24-animation-rigging-module-meeting/34813#keychannelbone-selection-in-the-dope-sheet-and-graph-editor-5). We decided that we should prioritize this, start a proper design task, and finally get this taken care of. No promises on a specific timeline, of course. But let's not let this last another five years. Some things to note from the module meeting discussion: - This may impact grease pencil, as some of its workflows apparently need channel/selection syncing to be a smooth/efficient user experience. - The reported behavior happens with bone selection in pose mode, but not with objects in object mode. So this is yet another weird case where animation features behave differently with bones than they do with objects. Whatever the design ends up being, it should be consistent between objects and bones.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Interest
Alembic

  
Interest
Animation & Rigging

  
Interest
Asset System
Asset datablocks, libraries, browser and shelf

  
Interest
Audio

  
Interest
Automated Testing

  
Interest
Blender Asset Bundle

  
Interest
BlendFile

  
Interest
Collada

  
Interest
Compatibility
Backward and forward 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
Wayland windowing on Unix

  
Interest
Workbench

  
Interest: X11

Xorg/X11 windowing

  
Legacy
Asset Browser Project

Archived

  
Legacy
Blender 2.8 Project

Archived

  
Legacy
Milestone 1: Basic, Local Asset Browser

Archived

  
Legacy
OpenGL Error

Archived

  
Meta
Good First Issue

  
Meta
Papercut

  
Meta
Retrospective

  
Meta
Security
Related to security, https://wiki.blender.org/wiki/Process/Vulnerability_Reports

  
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

Archived

  
Type
Report

  
Type
To Do

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
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
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
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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
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#71615
No description provided.
Delete Branch "%!s()"

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?