← All ideas
  • Published 2 Jul 2021

Weird group/collection collapsing behaviour

This is my scene hierarchy:

27b819a0ac57e769e3a9e48999074a15924098b7.jpeg

When you left-cick on the arrow next to Collection 1 you collapse the hierarchy beneath it, but when you shift left-cick 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-cick on an fully opened hierarchy to collapse it. Quite unintuitive , isn’t it?

Please don’t say you would need to familiarise yourself with the new way this works, that is not an excuse for unintuitive design. Shift left-cicking on an open object, the arrow next to it is pointing down, should completely collapse it, no matter whether the objects beneath it are open or not.

66.7%

Development Status: Open

Upvote 2 Downvote 1
LalaGhost
2 Jul 2021

7 Comments

dfer

I also find this unintuitive! If an arrow shows something is uncollapsed, shift+clicking should fully collapse it, and vice versa, whether it was full uncollapsed or just partially uncollapsed - after all, it's impossible to tell at a glance which of those two states something is in

1
bestelix

Maybe it's something in your settings because it works to collapse with shift click in all cases. I just tested in the latest alpha.

LalaGhost Author

I am using 2.93, it always first opens the whole hierarchy before closing it Maybe it is fixed in the latest alpha?

bestelix

Now I understand. But expand all/ collapse all toggles a tree property completely separate form the current item collapsed/expanded property.

LalaGhost Author

But the question then is whether it makes sense to be separate or not, right?

bestelix

As an added layer of control I think it's fine. The clicked item it's only relevant as a starting point evaluating down the branch state.

1

I'm using 2.93.0 and this is the behavior. It just "feels wrong" to me: when I shift click a 'collaped' arrow, right now it's impossible to predict what it's going to do without also checking every child object! So @lalaghost's suggestion makes a lot of sense to me! Why not switch to the more predictable way of doing it? so shift clicking a closed arrow woudl always expand all, and vice versa, instead of right now where you don't know what it's gonna do :-)

1