(Yes, I know this horse has already been severely beaten to death, but I bumped into this issue again today, and the most basic version of this shouldn't be much work to implement [just being able to child to a game object, no nested collections of collections], and I really can't think of any feature that is more fundamental to the engine, but isn't there)
Expected behaviour
Dragging a collection to a game object should child it
Actual behaviour
Action not allowed in editor, but can be done in script code via set_parent message.
How should this work? When you child with set_parent in script you need to child each go by itself or a hierarchy starting with a root GO. When dragging a collection, should then editor "dissolve" the collection and child each go separately, or are you talking about a new concept of being able to place collections anywhere in the scene graph?
Everything that is in the root of the collection should be parented to the game object you child the collection to. Nothing more fancy than that. It is what you expect will happen when you do that type of operation.
Just to clarify: the operation you suggest is equivalent to marking all GOs in a collection, press ctrl-c, then marking a target parent GO and pressing ctrl-v?
(Yes, I know this horse has already been severely beaten to death, but I bumped into this issue again today, and the most basic version of this shouldn't be much work to implement [just being able to child to a game object, no nested collections of collections], and I really can't think of any feature that is more fundamental to the engine, but isn't there)
Expected behaviour
Dragging a collection to a game object should child it
Actual behaviour
Action not allowed in editor, but can be done in script code via set_parent message.
How should this work? When you child with set_parent in script you need to child each go by itself or a hierarchy starting with a root GO. When dragging a collection, should then editor "dissolve" the collection and child each go separately, or are you talking about a new concept of being able to place collections anywhere in the scene graph?
Everything that is in the root of the collection should be parented to the game object you child the collection to. Nothing more fancy than that. It is what you expect will happen when you do that type of operation.
Just to clarify: the operation you suggest is equivalent to marking all GOs in a collection, press ctrl-c, then marking a target parent GO and pressing ctrl-v?
No. It is more like this:
Rather than currently only being able to do this:
Be able to do this: