Forum: FXRuby Should I usually use destroy()?

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
5b972395a92333843018b4add8af0437?d=identicon&s=25 Damián M. González (igorjorobus)
on 2012-06-03 19:11
Hi, I’m developing an application with this beautifull framework, had
read the book by Lyle Johnson by the way. I’m wondering if I should call
destroy() in those widgets which I’ll not use anymore.
Here is the real example: when I push a button, a FXDialogBox object
raise, it content is dynamic, what I mean is that it content will be
random, sometimes you will see a bunch of widgets, sometimes you will
see another different bunch of widgets, the question is: Should I call
destroy() in that FXDialogBox object?(I will not use the SAME dialog box
anymore) or ruby will take care of it.
What I learned reading the book is that the object in the CLIENT SIDE
will be erased by the Ruby GC when it is unavailable to reach by another
object or scope in the runtime(classic work of the GC, nothing strange);
by other side I’m not pretty sure about what happen with the SERVER SIDE
resource created in the past by that object now erased by the GC, what
happen with that? it’s erased from the Windows GDI? should I call
destroy() once I don’t need anymore the group of widgets?
Hope I was clear in explanation, thanks for your time.
5b972395a92333843018b4add8af0437?d=identicon&s=25 Damián M. González (igorjorobus)
on 2012-06-17 15:31
This is the answer by the way...
This topic is locked and can not be replied to.