There is still a problem with the disposeChildren method I created in that there are still a couple of classes, namely Table, that crap out on hasChildren. You get an error that obj.getChildren doesn't exist or something like that. I ended up having to create a layout to contain the 'body' information and when I needed to replace that information I simply dispose of the 'body' (sounds funny) and recreate it, never using removeAll.
Jim
On 9/21/06, dperez <[EMAIL PROTECTED]> wrote:
Sebastian,
Don't you remember that I discovered that removeAll() doesn't dispose
children, just changes their parent?.
Sebastian Werner wrote:
>
> remove and removeAll should definitely work. There are examples (in
> test) which shows this. And it's working. Maybe a *small* example would
> be helpful.
>
--
View this message in context: http://www.nabble.com/Disposing-of-objects-tf2036381.html#a6423136
Sent from the qooxdoo-devel mailing list archive at Nabble.com.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
