Parented objects get unparented when dragging said parent from one collection to another. #70061

Closed
opened 2019-09-19 11:05:55 +02:00 by Martin Durhuus · 7 comments

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
**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
Author

Added subscriber: @MartinDurhuus

Added subscriber: @MartinDurhuus
Member

Added subscribers: @natecraddock, @dfelinto, @lichtwerk

Added subscribers: @natecraddock, @dfelinto, @lichtwerk
Member

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 @dfelinto , @Zachman

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 @dfelinto , @Zachman

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

image.png

  • Select hierarchy has some improvements waiting on D5817: Outliner: Selection cleanup and #69212 (Outliner Sync Selection: Use general update method). Some outliner operators were selecting objects, but with syncing they can now select just outliner elements and let syncing do the viewport selection.
  • I haven't looked at this operator, but I also saw the same issues with the 3D view "Select Hierarchy operator"
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 ![image.png](https://archive.blender.org/developer/F7758213/image.png) * Select hierarchy has some improvements waiting on [D5817: Outliner: Selection cleanup](https://archive.blender.org/developer/D5817) and #69212 (Outliner Sync Selection: Use general update method). Some outliner operators were selecting objects, but with syncing they can now select just outliner elements and let syncing do the viewport selection. * I haven't looked at this operator, but I also saw the same issues with the 3D view "Select Hierarchy operator"

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Dalai Felinto self-assigned this 2019-09-19 15:09:39 +02:00

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
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
Member

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...)
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...)
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#70061
No description provided.