I just wanted to pass along some information I just learned about the way
parenting is done with the new .8 framework.
I use a pooling scheme and in .7, all I needed to do was to set the parent
of an object to null then move it to the pool. Everything worked great. So
along came .8 and there is no getParent on most objects, but there is a
getLayoutParent. In the comments for getLayourParent it says "gets the
parent of the object". So, I simply changed all my code to
setLayoutParent(null) and it 'looked' like everything was just great. In
reality, only the visible object was removed. If you actually query the
parent object you will see that the child still belongs to it. I think this
is a bug myself, but that's not for me to say. So, what I had to do, was to
replace all my this.setParent(null) statements with
this.getLayoutParent().remove(this). Then it gets visibly removed from the
parent and if you query the parent it no longer owns the object in question.
Just some possibly valuable information that you can use. I needed it
because just setting the layout parent to null left the object behind and
anything new I added to the parent got placed in all sorts of locations
except where I wanted them (because the old controls were still there, you
just can't see them).
Jim
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
