Page MenuHome

Collections viewport UI: show only non-excluded and hierarchy depth
Needs ReviewPublic

Authored by Dalai Felinto (dfelinto) on Sat, Jun 22, 1:56 AM.

Details

Summary

The viewport collections panel show hierarchy now.

We add a new setting which let users set the hierarchy depth they
want to see of the collections in the viewport collections panel.

This way we can show them in an hierarchical yet controlled way.

The same setting and display order is used for the "Hide Collection" operator.
This is accessed with [alt]1-10 or Ctrl+H.

Note: I think this operator should move to bpy.ops.view3d (it is in
bpy.ops.object now). We are past API changes so I'm not touching this.

Diff Detail

Repository
rB Blender
Branch
dev-collections (branched from master)
Build Status
Buildable 3913
Build 3913: arc lint + arc unit

Event Timeline

Preview of the interface:

With the Ctrl+H menu we can't have the padding to show hierarchy since it is a menu and I can't draw more than one element in the line (and for the padding I need to draw a few icons).

Note this would be for 2.81, since the UI is frozen and I want to spend time helping get Blender more stable rather than UI design.

Note this would be for 2.81, since the UI is frozen and I want to spend time helping get Blender more stable rather than UI design.

+1 . At least we will enter 2.81 with a solution to that. I poke you again once 2.80 is out so we can re-visit this topic.

Hi!

Interestnig solution.

But the problem is that autonumeration is dynamic. That means, it requires more memory to remember which number belongs to which collection depending on current depth state. For example, if user want to send objects to Collection with number 5 via pressing M5, it is hard to say where objects will be sent.

So it will be better if first 20 slots, that available for numerals keypressing, will have static (adress) autonumeration independently of hierarchy depth, but with numeration starting from first level of hierarchy.

Static autonumeration is looking not so fancy as dynamic but is more usable.
Example - when scene's collections are formed, user can call collection as "1_Room", "2_Car", "3_Table" during single scene setup, and this numeration in static representation will be actual independently of depth parameter.

Here is numeration types comparizon
B2 type is the best one, because of this issue
https://developer.blender.org/T61492