Organizing Nested Collections Activates Deactivated Children #81545

New Issue

Daniel Houghton · 2020-10-08T16:38:15+02:00

Daniel Houghton commented

2020-10-08 16:38:15 +02:00

System Information
Operating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18

Blender Version
Broken: version: 2.90.1, branch: master, commit date: 2020-09-23 06:43, hash: 3e85bb34d0
Worked: (newest version of Blender that worked as expected)

Short description of error
If you have a collection nested within another collection:

A
- B

and both collections are deactivated (checkbox is unchecked)

and you move A into a collection that is activated (checkbox checked)

then B becomes activated.

This is a bit of a problem when organizing high poly objects in collections as suddenly the high poly objects activate when I'm not expecting them to.

Exact steps for others to reproduce the error
From the default scene:

Add Cube.001, move it to the side so you can see it and move it into a New Collection called A
Add Cube.002, move it to the side so you can see it and move it into a New Collection called B
Move B into A to create the hierarchy below

A
- B
  - Cube.002
Cube.001

Deactivate B first and then deactivate A (uncheck the checkboxs)
Move A (which will take B with it) into Collection
Notice how B becomes activated even though it shouldn't.

Thanks for taking a peek at this!!
Daniel

**System Information** Operating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18 **Blender Version** Broken: version: 2.90.1, branch: master, commit date: 2020-09-23 06:43, hash: `3e85bb34d0` Worked: (newest version of Blender that worked as expected) **Short description of error** If you have a collection nested within another collection: - A - B and both collections are deactivated (checkbox is unchecked) and you move A into a collection that is activated (checkbox checked) then B becomes activated. This is a bit of a problem when organizing high poly objects in collections as suddenly the high poly objects activate when I'm not expecting them to. **Exact steps for others to reproduce the error** From the default scene: 1) Add Cube.001, move it to the side so you can see it and move it into a New Collection called A 2) Add Cube.002, move it to the side so you can see it and move it into a New Collection called B 3) Move B into A to create the hierarchy below - A - B - Cube.002 - Cube.001 4) Deactivate B first and then deactivate A (uncheck the checkboxs) 5) Move A (which will take B with it) into Collection 6) Notice how B becomes activated even though it shouldn't. Thanks for taking a peek at this!! Daniel

Daniel Houghton commented

2020-10-08 16:38:15 +02:00

Added subscriber: @DanielHoughton

Hans Goudey commented

2020-10-09 00:26:27 +02:00

Added subscriber: @HooglyBoogly

Hans Goudey self-assigned this 2020-10-09 00:26:27 +02:00

Hans Goudey commented

2020-10-09 00:26:27 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Hans Goudey commented

2020-10-09 00:26:27 +02:00

Hi Daniel! I do think this is a bug.

The code is pretty complicated here, but as far as I can tell all the "view layer collections" you see in the outliner are
created and destroyed whenever you move a collection, and these store the flags like the "exclude" one that was reset.
So the flags need to be copied over. But the existing code doesn't do that for the collection's children.

Maybe the problem is simpler than this, or completely different, we'll see!

Hi Daniel! I do think this is a bug. The code is pretty complicated here, but as far as I can tell all the "view layer collections" you see in the outliner are created and destroyed whenever you move a collection, and these store the flags like the "exclude" one that was reset. So the flags need to be copied over. But the existing code doesn't do that for the collection's children. Maybe the problem is simpler than this, or completely different, we'll see!

Bastien Montagne commented

2020-10-09 11:56:50 +02:00

Added subscriber: @mont29