Dopesheet Display Hidden doesn't work property combined with Only Selected. #68313

Open
opened 2019-08-06 14:33:29 +02:00 by Loris Libero · 27 comments

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

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f5449
Worked: Version 2.79b

Short description of error
In version 2.79 with the "Selection Only" option active in the dope sheet screen, after animating the appearance or disappearance of the object, you had the possibility to edit the keyframes, now it is possible only if the Only Selected option is deactivated, it is rather uncomfortable compared to the previous one because that option is useful to avoid having a max dopesheet window and to avoid errors in complex animations.

Exact steps for others to reproduce the error
Frame 1:
Turn off the object then Animate Disable in viewport,
Frame 2:
Turn on the object and animate Disable in viewport.
Open dopesheet window, Click Selection only and Display Hidden option at frame 2, go to frame 1 the frames disappear.

Dopesheet_280.blend
Dopesheet_279b.blend

**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86 **Blender Version** Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: `f6cb5f5449` Worked: Version 2.79b **Short description of error** In version 2.79 with the "Selection Only" option active in the dope sheet screen, after animating the appearance or disappearance of the object, you had the possibility to edit the keyframes, now it is possible only if the Only Selected option is deactivated, it is rather uncomfortable compared to the previous one because that option is useful to avoid having a max dopesheet window and to avoid errors in complex animations. **Exact steps for others to reproduce the error** Frame 1: Turn off the object then Animate Disable in viewport, Frame 2: Turn on the object and animate Disable in viewport. Open dopesheet window, Click Selection only and Display Hidden option at frame 2, go to frame 1 the frames disappear. [Dopesheet_280.blend](https://archive.blender.org/developer/F7651592/Dopesheet_280.blend) [Dopesheet_279b.blend](https://archive.blender.org/developer/F7651591/Dopesheet_279b.blend)
Author

Added subscriber: @loris.libero

Added subscriber: @loris.libero

#100635 was marked as duplicate of this issue

#100635 was marked as duplicate of this issue

#87552 was marked as duplicate of this issue

#87552 was marked as duplicate of this issue

#86694 was marked as duplicate of this issue

#86694 was marked as duplicate of this issue

#80074 was marked as duplicate of this issue

#80074 was marked as duplicate of this issue

#74402 was marked as duplicate of this issue

#74402 was marked as duplicate of this issue

Added subscriber: @DanielPaul

Added subscriber: @DanielPaul

Same behavior in 2.8.
When switching to the timeline, show hidden isn't taken into account at all.
The keyframes just disappear when the object is invisible.

Maybe there has to be made some discussion on how hidden objects are handled in general.
It's pretty confusing right now, especially when the visibility of objects is used extensively.

https://devtalk.blender.org/t/why-invisible-objects-are-bad/8496

@brecht Does this topic fit under the module "User Interface"?

Same behavior in 2.8. When switching to the timeline, show hidden isn't taken into account at all. The keyframes just disappear when the object is invisible. Maybe there has to be made some discussion on how hidden objects are handled in general. It's pretty confusing right now, especially when the visibility of objects is used extensively. https://devtalk.blender.org/t/why-invisible-objects-are-bad/8496 @brecht Does this topic fit under the module "User Interface"?

Added subscriber: @brecht

Added subscriber: @brecht

Removed subscriber: @DanielPaul

Removed subscriber: @DanielPaul

Added subscriber: @DanielPaul

Added subscriber: @DanielPaul
Member

Added subscribers: @WilliamReynish, @dfelinto, @lichtwerk

Added subscribers: @WilliamReynish, @dfelinto, @lichtwerk
Member

Hm, iirc disabled pretty much enforces unselected in 2.8.
So even if we disable the check here https://developer.blender.org/diffusion/B/browse/master/source/blender/editors/animation/anim_filter.c$3026, we still dont get the hidden object included in the dopesheet.

In a way 2.8 is more consistent here [no selection for hidden stuff, @dfelinto: correct me if I am wrong] but I can see this being handy, not sure what the best solution here might be? CC @WilliamReynish

Hm, iirc disabled pretty much enforces unselected in 2.8. So even if we disable the check here https://developer.blender.org/diffusion/B/browse/master/source/blender/editors/animation/anim_filter.c$3026, we still dont get the hidden object included in the dopesheet. In a way 2.8 is more consistent here [no selection for hidden stuff, @dfelinto: correct me if I am wrong] but I can see this being handy, not sure what the best solution here might be? CC @WilliamReynish
Sybren A. Stüvel changed title from Dopesheet Display Hidden dosent't work property combined with Only Selected. to Dopesheet Display Hidden doesn't work property combined with Only Selected. 2019-12-06 15:23:34 +01:00

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren

IMO the current approach that only visible objects can be selected is a sane one; this prevents a whole range of issues where people are performing changes to objects without knowing about those changes, because they wouldn't see all selected objects. In this particular case it backfires, though.

Would it be enough if we could pin an object to the Dope Sheet and Graph Editor in the same way we can in the Properties editor? That way you would be able to keep the cleanlyness of 'Selected Only' (i.e. no clutter from unselected object's animation curves) and still keep the object available in the Dope Sheet & Graph Editor.

IMO the current approach that only visible objects can be selected is a sane one; this prevents a whole range of issues where people are performing changes to objects without knowing about those changes, because they wouldn't see all selected objects. In this particular case it backfires, though. Would it be enough if we could pin an object to the Dope Sheet and Graph Editor in the same way we can in the Properties editor? That way you would be able to keep the cleanlyness of 'Selected Only' (i.e. no clutter from unselected object's animation curves) and still keep the object available in the Dope Sheet & Graph Editor.

Added subscribers: @Hjalti, @LucianoMunoz
Removed subscriber: @brecht

Added subscribers: @Hjalti, @LucianoMunoz Removed subscriber: @brecht

@Hjalti @LucianoMunoz do you have any insights to share here?

@Hjalti @LucianoMunoz do you have any insights to share here?

To be honest I preffered that you could select objects that are invisible,
In all my experience I dont recall any time modifiying something that was invisible unintendedly in 2.79.

Anyways I think the more sensible way:
only selected and the display hidden option are on by default, but hidden objects should appear in the dopesheet when both this options are on and the object is selected in the outliner.

To be honest I preffered that you could select objects that are invisible, In all my experience I dont recall any time modifiying something that was invisible unintendedly in 2.79. Anyways I think the more sensible way: only selected and the display hidden option are on by default, but hidden objects should appear in the dopesheet when both this options are on and the object is selected in the outliner.
Member

@dr.sybren: I guess it is up to you to somewhat make a decission on this?
[ just want to get this out of the "Needs triage by Developer" limbo... since these pop up on my desk over and over again ;) -- and we already have kind of meta-reports flying in, see {#72568}]

@dr.sybren: I guess it is up to you to somewhat make a decission on this? [ just want to get this out of the "Needs triage by Developer" limbo... since these pop up on my desk over and over again ;) -- and we already have kind of meta-reports flying in, see {#72568}]

As far as I can see, this is behaving as designed. There are clearly shortcomings in that design, but that doesn't make this a bug.

In #68313#825310, @LucianoMunoz wrote:
Anyways I think the more sensible way:
only selected and the display hidden option are on by default, but hidden objects should appear in the dopesheet when both this options are on and the object is selected in the outliner.

This makes sense, but is technically hard to do. The "selected in the outliner" state is per outliner. That means it's harder to get that selection state into the dopesheet/graph editor. Another problem is that it's not a global state. There can be two outliners, and they can have different selection states. Even worse, an object can be in multiple collections at the same time, and be selected in the outliner in one, but not on the other. Here is a screenshot that shows all this:

image.png

I'll change the type of this report to a Design task, as this needs to be well thought out and isn't something that can be quickly fixed.

As far as I can see, this is behaving as designed. There are clearly shortcomings in that design, but that doesn't make this a bug. > In #68313#825310, @LucianoMunoz wrote: > Anyways I think the more sensible way: > only selected and the display hidden option are on by default, but hidden objects should appear in the dopesheet when both this options are on and the object is selected in the outliner. This makes sense, but is technically hard to do. The "selected in the outliner" state is per outliner. That means it's harder to get that selection state into the dopesheet/graph editor. Another problem is that it's not a global state. There can be two outliners, and they can have different selection states. Even worse, an object can be in multiple collections at the same time, and be selected in the outliner in one, but not on the other. Here is a screenshot that shows all this: ![image.png](https://archive.blender.org/developer/F8237271/image.png) I'll change the type of this report to a Design task, as this needs to be well thought out and isn't something that can be quickly fixed.

Added subscriber: @laure

Added subscriber: @laure
Member

Added subscriber: @SpectreFirst

Added subscriber: @SpectreFirst

Added subscriber: @sidenkoai

Added subscriber: @sidenkoai

Hi! This thing still doesn't work.
I suggest to not to hide at least active object's curves and keys because 'active' state is global and it's the same in any editor.
btw it's broken in Drivers editor too.

Hi! This thing still doesn't work. I suggest to not to hide at least active object's curves and keys because 'active' state is global and it's the same in any editor. btw it's broken in Drivers editor too.
Member

Added subscriber: @BuzzKirill

Added subscriber: @BuzzKirill
Member

Added subscribers: @cheeseyscones, @erminos, @L0Lock

Added subscribers: @cheeseyscones, @erminos, @L0Lock
Member

Added subscribers: @candreacchio, @PratikPB2123

Added subscribers: @candreacchio, @PratikPB2123
Philipp Oeser removed the
Interest
Animation & Rigging
label 2023-02-09 14:36:40 +01:00
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
9 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#68313
No description provided.