Weird group/collection collapsing behaviour #90038
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#90038
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?
System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89
Blender Version
Broken: version: 2.93.0, branch: master, commit date: 2021-06-02 11:21, hash:
84da05a8b8
Short description of error
This is my scene hierarchy:
When you left-click on the arrow next to Collection 1 you collapse the hierarchy beneath it, but when you shift left-click on the arrow you open the full hierarchy beneath it, even though the arrow always works like a toggle, but not in this case. You can only shift left-click on an fully opened hierarchy to collapse it. Quite unintuitive , isn’t it?
Exact steps for others to reproduce the error
weirdCollapsingBehaviour.blend
Added subscriber: @LalaGhost
Added subscriber: @PratikPB2123
Thanks for the report. I think this is expected.
Shift + LMB
will expand all the data blocks of the parent. So in following case it will first expand all child data blocks of Cube then on another attempt it will collapse the list.(Will check the code to confirm if this is intentional)
Changed status from 'Needs Triage' to: 'Archived'
Looked at the code. Can say this is expected.
Present logic checks if flag
TSE_CLOSED
is set or not for every element present in the outliner. If at least one parent data block has the flag value set then all the unexpanded data block will expand.If not a single element has
TSE_CLOSED
flag set then functionoutliner_flag_is_any_test
will return 0 to unset the flagTSE_CLOSED
. Which means the list will collapse.In other words, list will expand even if the single Parent block is not expanded.
I will close the report since this is expected. Feel free to comment if reported problem is different than what I consider.
(Developers can correct if commented explanation is wrong)
It is rather that this behaviour is unintuitive rather than "wrong" on a code level.
Since a LMB works as a toggle on the arrows wouldn't it make more sense that the Shift + LMB works as a toggle, too?
Proposal:
Case:
Hierarchy is collapsed completely, arrow of parent is pointing to the right
Shift + LMB on the arrow of the parent expands the hierarchy and all its childrens hierarchy
Case:
Hierarchy is expanded completely, arrow is pointing to the bottom, as well for all children
Shift + LMB on the arrow of the parent collapses the hierarchy, so that the children are hierarchely hidden
Case:
Hierarchy is expanded partially, arrow of parent is pointing to the bottom, but childrens arrow point to the right
Shift + LMB on the arrow of the parent collapses the hierarchy, so that the children are hierarchely hidden
The third case is the only difference to the current behaviour and would underline the toggle nature of the clicks on the arrows
Why was this closed?