> Thank you. That was what I needed to know. I have several "extend :
> qx.ui.container.Composite" type objects that I will be creating and
> destroying many times throughout the lifetime of the application. From
> what you said it implies I need to make sure to clean up all the objects.
yes,
Thank you. That was what I needed to know. I have several "extend :
qx.ui.container.Composite" type objects that I will be creating and
destroying many times throughout the lifetime of the application. From
what you said it implies I need to make sure to clean up all the objects.
For objects
Hi,
the answer depends on your use case. qooxdoo has no garbage collection
or some think like this. qooxdoo dispose only qooxdoo objects on
shutdown (triggered from the unload event).
So if you have a class, which is used the complete application runtime,
it it not so important to keep the r
Is it even necessary for me to dispose of qx objects that are contained by
other qx objects. For example if I do something in my constructor like:
var groupBox = new.ui.groupbox.GroupBox("Stuff");
this.setLayout(new qx.ui.layout.VBox());
this.add(groupBox);
do I need to set references to the gr
Hi ,
there shouldn't occur any warnings for attributes with a prefix "$$".
This is a bug, see:
http://bugzilla.qooxdoo.org/show_bug.cgi?id=3867
Cheers,
Chris
Am 22.07.2010 16:52, schrieb arnis_andy:
> I have a "best practices" question.
>
> I have created several composite objects that have m
I have a "best practices" question.
I have created several composite objects that have member widgets. For the
the "sub-widgets" I create I use member object references that I make sure
to destruct. However, I realized after trying to track down a memory leak I
was causing with a List and ListI
