I'm noticing, looking over the dialog code, that people don't seem to be paying attention to memory management with gtkmm.
Now, it may be that folks aren't bothering, simply because the dialogs never get freed, but I'd still rather people do it properly.
Here is an explanation of how memory management is supposed to work in gtkmm. In most of the cases I've seen, the remedy is as simple as adding manage() around the creation of a widget.
http://www.gtkmm.org/gtkmm2/docs/tutorial/html/ch18.html
Fingers off the about dialog, though, I've got that one.
-mental
On Sat, 2005-11-26 at 13:38 -0500, MenTaLguY wrote:
I'm noticing, looking over the dialog code, that people don't seem to be paying attention to memory management with gtkmm.
Now, it may be that folks aren't bothering, simply because the dialogs never get freed, but I'd still rather people do it properly.
Here is an explanation of how memory management is supposed to work in gtkmm. In most of the cases I've seen, the remedy is as simple as adding manage() around the creation of a widget.
http://www.gtkmm.org/gtkmm2/docs/tutorial/html/ch18.html
Fingers off the about dialog, though, I've got that one.
Okay, I'm a touch confused. Does this mean that GTKmm doesn't do refcounting like GTK+ normally does? Or is this only when I'm subclassing a GTKmm widget? Why doesn't the normal GTK+ 'destruction' work in GTKmm?
--Ted
participants (2)
-
MenTaLguY -
Ted Gould