i did the same thing on the skincast.. i should never assume.. sorry sViz!
No worries, DA (and Zubaz), at least you pronounced my nick right.
I guess I should clarify that setting or assigning a parent wasn't the problem. I can do that. The specific problem was setting
object.child = "yes" or
object.child = "no". The distinction was important because, as you know, that allows/disallows the child object to be visible outside the parent's boundaries.
sounds like something we need to add to the DesktopX.info Site!
I'll be sure to put it in the tutorial section on the site, because it requires a good deal of explaining.
For what it's worth:
My idea was, on dragfinish, depending on where I dropped an object, it would either:
1. create a new object, which was not a child
2. if I drop it on another object it would automatically set the parent and make it a child.
To create the object as a child I had to clone a template object which was already a child of another object and then just change the parent (I did this before with my eZbrowser). The problem was making it not a child after cloning.
I could set the parent to nothing but then, checking its properties, it was still set to child = "yes". So it was a child of nothing and it wasn't visible!
After fuddling around I decided to clone the clone again and see what happens....it worked. The 2nd clone, without a parent, was automatically set to child = "no"
Crazy, huh? Well, all in a day's work.
