Parent - Child relationship changes?

Am I correct that now when you set an object as an non-contained child of another object, rather than
actually doing that, it makes it a child of the 'parent of the new parent'??

Maybe a stepped through example...

This is what I 'want':

Parent 1

Parent 2 (child of Parent 1 - contained)

Child 1 (child of Parent 2 - non contained - events go to Parent 2)

 

This is what I 'get':

Parent 1

Parent 2 (child of Parent 1 - contained)

Child 1  (child of Parent 1 - no events go to Parent 2)

I think I understand the 'reasoning' behind this (some sort of 'optimisation', but it creates a number of flaws

1. Events don't go to the parent you want them to go to
2. Z-order can be buggered up, Children should be above parents (or has been the way in the past)

6,434 views 3 replies
Reply #1 Top
Example of this -
http://www.freewebtown.com/skarn/downloads/chilbug1.desktop

Try to set the blue blog as a NON CONTAINED child of Parent2
Nomatter what you do, it seems to always put it as a NON Contained child of Parent1

If this WORKS for someone, please let me know, because then I can investigate other causes.

DesktopX version: 3.49f[rc].016 Professional
Reply #2 Top
confirmed behaviour - I noticed this first when I was using script to set an object's parent and thought it was just a scripting error, but the same thing happens when I try to set the parent thru the properties sheet.

not sure if it's a bug or intentional behaviour tho