Outliner: Synced Selection #63988

Closed
opened 2019-04-29 16:41:03 +02:00 by William Reynish · 11 comments

In Blender, the selection state is not shared between the Outliner and the scene. This is inconvenient and often impractical, but it’s also confusing. If you select something in the viewport, the same object is not selected in the Outliner. But if you select something in the Outliner, it overrides the selection inside the viewport. The selection is synced one way but not the other. It’s half syncing in a confusing way.

It also means that we need two confusing ways of showing selections - the highlighted row and the icon circle.

I think we can make this a lot easier to use. Here’s how:

We add a toggle inside the Filter popover called Synced Selection, just like we have in the UV Editor. This should be on by default.

Screenshot 2018-12-07 at 21.07.08.png

Synced Selection: On

With this option on, the selection state is shared between the Outliner and the viewport. This makes everything simpler, because users don’t have to worry about selecting things twice. If something is selected, it’s selected in both Outliner and viewport, always.

One of the great benefits of this, is that we then don't need two separate selection states inside the Outliner, which makes it much simpler to read and understand.

Screenshot 2018-12-07 at 21.07.48.png

Synced Selection: Off

With this option off, the selection state is completely decoupled, rather than the current half-syncing system that tries to only sync one way. This could mainly be useful if you have multiple Outliners with different selections.


These changes should make selection in the Outliner a lot more straight forward, in a way that’s both more efficient and less confusing in the vast majority of use-cases.

Special Cases

When simply selecting objects in the Outliner, it's easy to figure out what to do. But there are other cases where it's not so clear:

Outliner Selection 3D View Result
Sub-element of object (obData, material etc) in Outliner Select the object they are attached to
Collection in Outliner Select containing objects
View Layer in Outliner Deselect all objects
In Blender, the selection state is not shared between the Outliner and the scene. This is inconvenient and often impractical, but it’s also confusing. If you select something in the viewport, the same object is not selected in the Outliner. But if you select something in the Outliner, it overrides the selection inside the viewport. The selection is synced one way but not the other. It’s half syncing in a confusing way. It also means that we need two confusing ways of showing selections - the highlighted row and the icon circle. I think we can make this a lot easier to use. Here’s how: We add a toggle inside the Filter popover called Synced Selection, just like we have in the UV Editor. This should be on by default. ![Screenshot 2018-12-07 at 21.07.08.png](https://archive.blender.org/developer/F5874632/Screenshot_2018-12-07_at_21.07.08.png) ## Synced Selection: On With this option on, the selection state is shared between the Outliner and the viewport. This makes everything simpler, because users don’t have to worry about selecting things twice. If something is selected, it’s selected in both Outliner and viewport, always. One of the great benefits of this, is that we then don't need two separate selection states inside the Outliner, which makes it much simpler to read and understand. ![Screenshot 2018-12-07 at 21.07.48.png](https://archive.blender.org/developer/F5874644/Screenshot_2018-12-07_at_21.07.48.png) ## Synced Selection: Off With this option off, the selection state is completely decoupled, rather than the current half-syncing system that tries to only sync one way. This could mainly be useful if you have multiple Outliners with different selections. -------- These changes should make selection in the Outliner a lot more straight forward, in a way that’s both more efficient and less confusing in the vast majority of use-cases. ## Special Cases When simply selecting objects in the Outliner, it's easy to figure out what to do. But there are other cases where it's not so clear: | **Outliner Selection** | **3D View Result** | | -- | -- | | Sub-element of object (obData, material etc) in Outliner| Select the object they are attached to | | Collection in Outliner | Select containing objects | | View Layer in Outliner | Deselect all objects |

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish
Dalai Felinto was assigned by William Reynish 2019-04-29 16:52:52 +02:00

Added subscriber: @DuarteRamos

Added subscriber: @DuarteRamos
William Reynish changed title from Outliner Synced Selection to Outliner: Synced Selection 2019-04-29 18:04:45 +02:00

Added subscriber: @Ghostil

Added subscriber: @Ghostil

Good idea. In the same 3d max it works synchronously with scene explorer.

Good idea. In the same 3d max it works synchronously with scene explorer.

This problem only in 2.8.
In 2.79 this normal selected and Synced outliner and 3d view.

This problem only in 2.8. In 2.79 this normal selected and Synced outliner and 3d view.

@Ghostil that is in fact not the case. It only tries to sync in one direction in both versions of Blender.

@Ghostil that is in fact not the case. It only tries to sync in one direction in both versions of Blender.

We have a choice to either include this as an option (enabled by default) or to simply change the behavior fully with no option. I don't have a strong opinion, as long as the default syncs the selection.

However, I expect there may be cases where we need to be able to turn it off, such as when users have multiple Outliners.

We have a choice to either include this as an option (enabled by default) or to simply change the behavior fully with no option. I don't have a strong opinion, as long as the default syncs the selection. However, I expect there may be cases where we need to be able to turn it off, such as when users have multiple Outliners.

Added subscriber: @ArmoredWolf

Added subscriber: @ArmoredWolf

Added subscriber: @natecraddock

Added subscriber: @natecraddock

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Committed in 71eb653280

Committed in 71eb65328078
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
5 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#63988
No description provided.