Hi there,
during investigations on another issue[1] I stumbled over a disposal issue that
I can not resolve by myself.
Both form renderer (qx.ui.form.renderer.Single and Double) bind the label and
the field item together in their "addItems()" method via
"label.setBuddy(item);".
Whenever I call the destructor of a form (with a renderer), the warning
appears.
But somehow I can't find the correct place to remove that buddy.
Doin' it in the destructor of qx.ui.basic.Label creates errors like:
----------------
The array field: __widgetChildren of object: qx.ui.container.Composite[707]
has non disposable entries: Error: The array field: __widgetChildren of
object: qx.ui.splitpane.Pane[1221] has non disposable entries: Error: The
array field: __widgetChildren of object: qx.ui.container.Composite[886] has
non disposable entries: Error: The array field: __widgetChildren of object:
qx.ui.tabview.Page[923] has non disposable entries: Error: The array field:
__widgetChildren of object: qx.ui.form.renderer.Single[1036] has non
disposable entries: Error: Binding could not be found!
----------------
Doin' it on destruction of the renderer (e,g, "qx.ui.form.renderer.Single"),
will give similar results...
I think it has more to do with the binding than anything else, but that's a
topic I've not been able to understand 100% by now ;)
I have managed to remove several other "Missing destruct definition!..."
warnings so far, but here I am "out of my latin" ;)
I would like to create a bug report for this, but I don't want to make one for
each occurrence of "Missing destruct definition!..."
Most of the 'other' warnings I've managed to kill so far are just plain
"nullable object properties", that have to be set to null in the
destructor like this:
<code>
properties :
{
someProp : {
nullable : true
}
},
destruct : function () {
this.setSomeProp(null);
}
</code>
The "check for missing disposals" should be managed in a kind of "reoccurring"
bug, shouldn't it? That would be something I couldn't do ;)
But if someone can maybe give me a hint on how to avoid these "buddy" warnings.
that would help me (and others?) a lot.
/Peter
[1]http://qooxdoo.678.n2.nabble.com/Bad-resource-leakage-tp5233776p5233776.html
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
