Page MenuHome

Unchecking and checking collection automatically checks all collections inside it
Closed, ArchivedPublic

Description

This is system independent and I have seen it both in 2.82 and 2.83.

As in the title unchecking and checking a collection back automatically checks all collections inside it and this is very bothering cause it makes obejct you eventually wanted to be invisible to cover your scene again and you have to manually hide'em again.

About visibility: Pressing number keys (those above letters) selects some objects to be visible disabling all the others, but since there are only 9 numbers, once one has more objects in the scene this feature only bothers the user since he has to manually make all the wanted objects visible again trying to figure out which one was visible before the command.

I know I can work around this by setting my keyboard to emulate numpad or map it differently but having such issues by default isn't so cool for Blender.

Event Timeline

It's nice that I am not the only one who finds the current behavior suboptimal :)
The patch is already waiting for review - D7016: Least Astonishment in LayerCollection.exclude

Good to see that there is a patch already dealing with this issue.
But I will have to close this report as it is not a bug but a request for modified/improved behavior.
And this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug