Page MenuHome
Create Task
Maniphest T70061

Parented objects get unparented when dragging said parent from one collection to another.
Closed, ArchivedPublic
Actions

Description

System Information
Operating system: Windows 10
Graphics card: GTX 1070

Blender Version
Broken: v 2.80 (Is what the splash screen says, can't see a build version here)

Short description of error
If you have an object in a collection, and that object has children; dragging the object
from one collection to another, in the Outliner, will result in the object being moved without its children.
The children will remain in the initial collection.

Exact steps for others to reproduce the error

  1. Duplicate the default cube
  2. Parent one to the other
  3. Create a new Collection in the Scene Collection
  4. In the Outliner, LMB click-and-hold the parent cube
  5. While holding, drag to the newly created Collection

Related Objects

Event Timeline

Martin Durhuus (dur) created this task.Sep 19 2019, 11:05 AM
Philipp Oeser (lichtwerk) lowered the priority of this task from 90 to 80.Sep 19 2019, 11:49 AM
Philipp Oeser (lichtwerk) added a project: User Interface.
Philipp Oeser (lichtwerk) added subscribers: Nathan Craddock (natecraddock), Dalai Felinto (dfelinto), Philipp Oeser (lichtwerk).

Dont think this is a bug really, but expected behavior?
(2.79 also did this for layers)
(it is generally easy to select the whole hierarchy (various ways) and proceed from there...)

While checking on this, there seem to be two problems in this regard:

  • the behavior of "Select Hierarchy" in the outliner (all children are selected, but it doesnt mark the objects as selected in the outliner, dragging to another collection will act as if only the parent was selected, dont think this is intentional?)
  • the behaviour of the "Select Hierarchy" operator in 3DView doesnt seem to work with Direction set to Child [will check on this]

For the remaining questions [bug?, Outliner Select Hierarchy?] I would like feedback of @Dalai Felinto (dfelinto) , @Zachman

Nathan Craddock (natecraddock) added a comment.Sep 19 2019, 2:40 PM

I'm pretty sure this isn't a bug, as the same behavior is used if Cube is moved to collection 2 from the viewport with "M > Collection 2". If only the parent cube is moved to the second collection, the outliner draws the child with a dashed line under it, showing the relationship, but implying that the child is in a different collection

Dalai Felinto (dfelinto) changed the task status from Unknown Status to Archived.Sep 19 2019, 3:09 PM
Dalai Felinto (dfelinto) claimed this task.

Thanks for the report, but this is not a bug, but the intended behaviour. It can get confusing because we are talking about two hierarchical system that work in parallel with no ties to each other:

  • Collections hierarchy
  • Parental hierarchy
Philipp Oeser (lichtwerk) added a comment.Sep 19 2019, 7:37 PM

quick note: checked on Select Hierarchy (the python one for the 3DView):

  • problem with Direction set to Child is just problematic if called from search [default Parent] and then wanting to REDO (set to Child), this isnt working because the operator cancels...
  • but we already have extensive menu entries in Select > Select More/Less, and these all do the work just fine...
  • (it is a bit inconsistent with the operator in the outliner [as in: the python one will only do one level, the outliner one will do recursive], but this can be handy at times so dont think this a problem either...)