[Bf-committers] View Layers and Collections (blog post)
mikhail.rachinskiy at gmail.com
Wed Sep 20 12:12:38 CEST 2017
I think default behavior should be to delete objects if their collection is
deleted, but only if they are not included in other collections. Otherwise
we'll end up with huge blend files containing "dead" objects in
bpy.data.objects but not in the actual scene.
I have a question about new scene structure:
In 2.79 to walk through all objects in the scene we can use scene.objects.
But in 2.8 one object can be assigned to multiple collections at once,
which means that we cannot use master collection to walk through all
objects, since we'll walk over the same object multiple times.
Is there a place in 2.8 we can access all objects in the scene once per
On Wed, Sep 20, 2017 at 1:43 PM, Dalai Felinto <dfelinto at gmail.com> wrote:
> Hi all,
> Ton Pablo and I put together a post explaining the collections in Blender
> This is a document aimed at end users. Its goal is to solidify new
> concepts (e.g., collections) and a new vocabulary (e.g., view layers).
> For developers following Blender 2.8 code some things are not
> literally as presented there. For instance, "conceptually" all objects
> of a scene are in the master collection. However, not all objects are
> directly in the master collection, but stored in a nested collection.
> That said, there are also things that are presented there that need to
> be implemented. As an example if you delete a collection now its
> objects go away as well. But we probably want them to go to the master
> collection. Or at we need at least "delete collection and objects /
> delete collection only" options.
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers