Outliner Improvements #58969
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
33 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#58969
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?
In Blender 2.8 we introduced Collections to manage our objects and scenes. This places more emphasis and reliance on the Outliner, and so now is a good time to make additional improvements to how it works.
Here are some areas that have potential to make the Outliner more delightful and easy to use.
Added subscriber: @WilliamReynish
#58968 was marked as duplicate of this issue
Added subscriber: @dfelinto
Added subscriber: @moisessalvador
Removed subscriber: @moisessalvador
Will you consider adding unlinked collections management to this design document? I made a small proposal to not use another outliner for orphan collections. I hope you check it out https://blender.community/c/rightclickselect/ltcbbc/
Added subscriber: @1D_Inc
Well, sounds nice and very welcome.
I've ordered to my developer selecting all outliner object between two selected (we've got too long lists for box selecting) just a few days ago, so Shift and Control modifiers are very needed.
Added subscriber: @lichtwerk
Added subscriber: @moisessalvador
@moisessalvador: Yes, an easier way to add unlinked Collections is fairly important I think. Currently it's both an arduous process, and very difficult to find.
I can think of several ways to go about this, one of which is something similar to your proposal.
@WilliamReynish : not sure if this is off-topic, but could we add multi-object-drag-drop for parenting to the list?
(right now it is possible to multi-object-drag-drop to collections -- but not to other objects [for parenting]... which seems a little inconsistent)
@lichtwerk: yes, this was already added to the Paper Cuts list, but I added a link to it here too.
Added subscriber: @elbox01
Hi, @WilliamReynish I am absolutely loving this improvements, they will make the "Outliner" more dynamic and more robust.
But would you take autoscroll-in-the-outliner into consideration?
Added subscriber: @JulienKaspar
I'm all for everything that's said in this proposal. The syncing of the selections could cause problems when a lot of linking is involved but that's why keeping it optional and either completely on or off is a great idea.
Added subscriber: @Mantasku
I wanted answer more from usability point of view.
Users cannot tidy up sorted lists, they just can bring a mess in it. If sorted list doesnot fits they needs, that means, that users messed up with object's naming.
So they have to wisely fix their naming or use collections to sort something out (as they were using layers in 2.79). Maybe both of them together.
@JulienKaspar are you even happy with D4011?
Removed subscriber: @moisessalvador
@dfelinto Sorry I was not able to try it out. Maybe you can send me a build. I can't really figure out what the 3 levels of outliner visibility means from the description alone.
I think there's another helpful feature I'd like to propose:
Currently when creating a new collection either with the shortcut "C" or with the collection button in the top-right corner, it will create a new empty collection under the one that is actively selected (the white circle behind a collection).
Often times I want to create a collection with my selection of objects being automatically moved to the new collection. But currently I have to select the active collection, create a new collection there and then hit M in the 3D Viewport to move the selection to the new collection by navigating a possibly long menu with many submenus.
The proposed synced selection can help with this but I'd suggest to add this:
The hitting C or the top-right button it will create a new collection below the actively selected collection but when objects are selected it will move the selection into the newly created collection and place the new collection in the top-most collection that the selected objects are nested in.
So in this example selecting the Sphere and Cube and then hitting C to create a new collection, instead of resulting in this:
it should result in this:
Ctrl is currently used for linking so this can be used here as well. When hitting Ctrl + C or Ctrl clicking the button the objects could be linked into the new collection:
If the placement of the new collection should still be inside the actively selected collection then that would be fine as well. I guess this can give extra control but always requires some extra attention of which collection has the white circle currently.
Another feature that I'm not sure I proposed before but would save me a lot of time is this:
Currently these are the top options when RMB clicking a collection.
The option that I am missing is "Duplicate Hierarchy". When duplicating a collection it links all contents instead of duplicating them as well, which can be very useful , but most of the time I want to duplicate the contents as well.
There's no easy way of doing this currently sicne duplicating the collections will always link the contents, so I have to create new collections, rename them, duplicate the objects I want in them and move them to the new collection, rinse & repeat for every nested collection.
Using M in the 2D viewport you can do just that. At the "bottom" of each of the levels of the menu you can move the objects to a new collection.
Sure I believe we could have this.
@dfelinto
True. It would be nice to have the possibility to do this in the Outliner as well though. Also in the M menu there is no way of creating a new nested collection.
The frustrating thing for me is navigating a dozen sub-menus when pressing M when I already have everything visible and selected in the Outliner as well.
Being able to do it in the Outliner as well would mean that I can do it all in the same Editor without needing the 3D Viewport for Outliner management and no extra long popup Menus.
Added subscriber: @DuarteRamos
This is really going the right way! With all items in this proposal implemented, and Shift-Click to fill selection enabled, the outliner finally becomes almost perfect, solving all previous limitations and shortcomings.
Only thing missing is making the toggles (visibility, selectability and renderability) affect all selected items, rather than just the one clicked, if possible.
Great work.
Added subscriber: @xCyborg
Added subscriber: @orvb
Added subscriber: @hadrien
This should probably be reversed to match current selection paradigm :
Added subscriber: @RobertS
That is the inverse to the current industry standard. The selection paradigm should follow what Microsoft has been doing with the File Explorer for the last three decades, otherwise new users will be confused.
The current outliner selection method and what you propose could be options, just as right click select has become.
Added subscriber: @xdanic
I have some more notes on improving the Outliner usability:
Added subscriber: @frameshift
@JulienKaspar: it’s a good list. It’s often times getting these kinds of smaller details right that make a real big difference. I would hope there’s time before release to look at improving the Outliner. We are relying on it more now, and it has some real annoyances still.
Since I had what I thought was a bug labeled as a feature request, I guess I'll add that here then instead:
Added subscriber: @DanielPaul
There is also need in "Isolate selected Collections" option on RMB menu, that will turn off every collection except collections that are not selected in outliner, or which contains no selected objects in outliner.
So if some objects selected in outliner belongs to 3 collections, all 3 of them will stay turned on, other unselected collections will turn off.
Previously, in 2.79, we made such tool in Bargool_1D_tools , called "Isolate layers".
It leaves turned on only those layers, that selected objects belongs to.
Simple, and extremely useful option for complex scenes, while layers were cumulative, just like collections.
Added subscriber: @machieb
Added subscriber: @wevon-2
I see it a bit confusing to link a collection of the blender file to the scene. I think it would be useful to call them from Layer View directly. Even a pop-up menu that shows all the collections and allows you to link and unlink directly, would be very useful, so you do not have to switch between Outlinier modes.
@wevon-2: Yes I thought of this too. Adding unlinked collections to your scene is still too obscure and difficult to find.
Added subscriber: @Lapineige
Added subscriber: @AlphaVDP2
Added subscriber: @zebus3dream
Added subscriber: @Garlash
Added subscriber: @ArmoredWolf
Added subscriber: @martinium
I support with both hands this outliner design features. They will make outliner both as mentioned more efficient and at the same time less confusing, but also closer to a 3ds max / Maya / other 3d apps outliner way of working which is good for new artists coming from other software.
Added subscriber: @TheCharacterhero-4
Added subscriber: @mois.moshev
Added subscriber: @Poulpator
@dfelinto @WilliamReynish I think I have found another thing that can be improved in the outliner.
outliner_show_active.mp4
If you are using "Show Active" in the outliner it will only show the selection in the first collection it appears in. This even happens when the object is just parented but not actually inside the collection itself.
It probably makes more sense to just show the selection in all collections.
Added subscriber: @erik85
I really do think all the Restriction toggles should be visible by default.. I mean they don't take up that much space do they?
I find it extremely annoying to enable them in all workspaces all the time. And I never find myself disabling any of them which should ring a bell.
Removed subscriber: @RobertS
Here are proposals about global functions in outliner for heavyweight (~1000 collections) setups.
A) Normal state - initial state of outliner
B) Ability to use ctrl+LMB outliner isolation as toggle, with restoring previous global state.
First ctrl+LMB press remembers inital state of scene visibility, and isolates collection, second - restores previous state of scene, stored by firts ctrl+LMB.
This will allow to quickly figure out what is stored in any collection.
C) Ability to invert visibility - to figure out what is hidden in scene. Red line is drawn in UI.
D) Ability to swap any column with visibility. This will allow to view and edit render/other state of objects of entire scene as visibilty for better scene handling and control. Column, that was swapped with visibility column became purple.
E) Ability to make everything visible via single toggle hotkey (maybe * key), to make sure what it contains during setup.
Here is GIF:
Removed subscriber: @frameshift
Added subscriber: @MassimilianoPuliero
yeah, "delete" in the outliner should actually eliminate the object from the scene.
Added subscriber: @zgorg
a parameter collection.name should be added in bpy.ops.outliner.item_activate to simulate a click and then make possible to use things like bpy.ops.outliner.collection_duplicate(), using a script...
Added subscriber: @Vyach
Short: I can disable all viewport objects in bulk with {key Alt LMB} But can enable em back same way. As far it is disable object selection, it is disable switching renderability with {key Alt}
2020-05-03_19-48-29.mp4
Removed subscriber: @machieb
Changed status from 'Confirmed' to: 'Resolved'