[gtkmm] Gtkmm-forge digest, Vol 1 #445 - 16 msgs
- From: gtkmm-forge-request lists sourceforge net
- To: gtkmm-forge lists sourceforge net
- Subject: [gtkmm] Gtkmm-forge digest, Vol 1 #445 - 16 msgs
- Date: Wed, 25 Jun 2003 10:17:46 -0700
Send Gtkmm-forge mailing list submissions to
gtkmm-forge lists sourceforge net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
or, via email, send a message with subject or body 'help' to
gtkmm-forge-request lists sourceforge net
You can reach the person managing the list at
gtkmm-forge-admin lists sourceforge net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gtkmm-forge digest..."
gtkmm-forge is the mailing list that receives gtkmm bug reports from bugzilla. A daily digest is sent to gtkmm-main, to encourage people to help fixing the bugs.
Today's Topics:
1. [Bug 113688] Changed - debian: No checkbox in TreeView for boolean fields (bugzilla-daemon widget gnome org)
2. [Bug 113688] Changed - debian: No checkbox in TreeView for boolean fields (bugzilla-daemon widget gnome org)
3. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
4. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
5. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
6. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
7. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
8. [Bug 91404] Changed - Gtk::Button: memory leak when using mnemonic=true. (bugzilla-daemon widget gnome org)
9. [Bug 91404] Changed - Gtk::Button: memory leak when using mnemonic=true. (bugzilla-daemon widget gnome org)
10. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
11. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
12. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
13. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
14. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
15. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
16. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
--__--__--
Message: 1
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, zsdebre telant tvnet hu
Cc:
Date: Wed, 25 Jun 2003 02:57:38 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 113688] Changed - debian: No checkbox in TreeView for boolean fields
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=113688
Changed by murrayc usa net
--- shadow/113688 Tue Jun 24 17:26:01 2003
+++ shadow/113688.tmp.4300 Wed Jun 25 02:57:38 2003
@@ -125,6 +125,9 @@
on debian.
------- Additional Comments From zsdebre telant tvnet hu 2003-06-24 17:26 -------
Yes, this --enable-maintainer-mode was new for me, as I'm new to gtkmm.
So the checkboxes are working correctly on Debian SID, using Cedric'
patch (g++-3.2.3). Thanks a lot!
+
+------- Additional Comments From murrayc usa net 2003-06-25 02:57 -------
+OK, well done guys. Cedric, please apply your patch.
--__--__--
Message: 2
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, zsdebre telant tvnet hu
Cc:
Date: Wed, 25 Jun 2003 03:18:17 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 113688] Changed - debian: No checkbox in TreeView for boolean fields
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=113688
Changed by cgustin ibelgique com
--- shadow/113688 Wed Jun 25 02:57:38 2003
+++ shadow/113688.tmp.13939 Wed Jun 25 03:18:17 2003
@@ -128,6 +128,10 @@
Yes, this --enable-maintainer-mode was new for me, as I'm new to gtkmm.
So the checkboxes are working correctly on Debian SID, using Cedric'
patch (g++-3.2.3). Thanks a lot!
------- Additional Comments From murrayc usa net 2003-06-25 02:57 -------
OK, well done guys. Cedric, please apply your patch.
+
+------- Additional Comments From cgustin ibelgique com 2003-06-25 03:18 -------
+Seems you already applied the patch to both branches on 2003-06-14.
+I guess we can change the status of this bug to resolved.
--__--__--
Message: 3
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
harald hopfes hopfes sysde eads net
Cc:
Date: Wed, 25 Jun 2003 03:24:24 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=114568
Changed by murrayc usa net
--- shadow/114568 Tue Jun 24 14:48:21 2003
+++ shadow/114568.tmp.16002 Wed Jun 25 03:24:24 2003
@@ -1092,6 +1092,17 @@
** (main:26364): WARNING **: Data of GtkVBox: refcount: 3
gtk_container_destroy: GtkVBox
gtk_widget_real_destroy: GtkVBox
gtk_object_real_destroy: GtkVBox
+
+------- Additional Comments From murrayc usa net 2003-06-25 03:24 -------
+OK, so my previous suggestion still seems to be relevant:
+"Maybe the destroy_notify is called when the GtkVBox widget is about
+to be destroyed. (There is a 2-stage destroy process in GTK+). And
+maybe it never actually gets destroyed because something stops the
+destroy process. I would investigate any destroy callbacks in GTK+
+for GtkVBox or its base "classes". I would throw a few debug
+statements in there."
+As an extra hint, I think that 2nd stage is called "dispose".
+
--__--__--
Message: 4
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
harald hopfes hopfes sysde eads net
Cc: murrayc usa net
Date: Wed, 25 Jun 2003 04:06:20 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=114568
Changed by harald bugzilla gnome org hopfes de
--- shadow/114568 Wed Jun 25 03:24:24 2003
+++ shadow/114568.tmp.318 Wed Jun 25 04:06:20 2003
@@ -1103,6 +1103,11 @@
maybe it never actually gets destroyed because something stops the
destroy process. I would investigate any destroy callbacks in GTK+
for GtkVBox or its base "classes". I would throw a few debug
statements in there."
As an extra hint, I think that 2nd stage is called "dispose".
+
+------- Additional Comments From harald bugzilla gnome org hopfes de 2003-06-25 04:06 -------
+Murry: Did you ever have the case before that the notify didn't get
+called? I mean in a previous bug. If so, what was that reason
+before?
--__--__--
Message: 5
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
harald hopfes hopfes sysde eads net
Cc:
Date: Wed, 25 Jun 2003 04:31:29 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=114568
Changed by murrayc usa net
--- shadow/114568 Wed Jun 25 04:06:20 2003
+++ shadow/114568.tmp.11566 Wed Jun 25 04:31:29 2003
@@ -1108,6 +1108,11 @@
------- Additional Comments From harald bugzilla gnome org hopfes de 2003-06-25 04:06 -------
Murry: Did you ever have the case before that the notify didn't get
called? I mean in a previous bug. If so, what was that reason
before?
+
+------- Additional Comments From murrayc usa net 2003-06-25 04:31 -------
+Hmm, I think this bugs had that problem:
+http://bugzilla.gnome.org/show_bug.cgi?id=111084
+
--__--__--
Message: 6
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
harald hopfes hopfes sysde eads net
Cc: murrayc usa net
Date: Wed, 25 Jun 2003 05:13:46 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=114568
Changed by harald bugzilla gnome org hopfes de
--- shadow/114568 Wed Jun 25 04:31:29 2003
+++ shadow/114568.tmp.29187 Wed Jun 25 05:13:46 2003
@@ -1113,6 +1113,10 @@
before?
------- Additional Comments From murrayc usa net 2003-06-25 04:31 -------
Hmm, I think this bugs had that problem:
http://bugzilla.gnome.org/show_bug.cgi?id=111084
+
+------- Additional Comments From harald bugzilla gnome org hopfes de 2003-06-25 05:13 -------
+I found another maybe relevant bug
+http://bugzilla.gnome.org/show_bug.cgi?id=91404
--__--__--
Message: 7
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
harald hopfes hopfes sysde eads net
Cc: murrayc usa net
Date: Wed, 25 Jun 2003 05:50:49 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=114568
Changed by harald bugzilla gnome org hopfes de
--- shadow/114568 Wed Jun 25 05:13:46 2003
+++ shadow/114568.tmp.15373 Wed Jun 25 05:50:49 2003
@@ -1117,6 +1117,22 @@
http://bugzilla.gnome.org/show_bug.cgi?id=111084
------- Additional Comments From harald bugzilla gnome org hopfes de 2003-06-25 05:13 -------
I found another maybe relevant bug
http://bugzilla.gnome.org/show_bug.cgi?id=91404
+
+------- Additional Comments From harald bugzilla gnome org hopfes de 2003-06-25 05:50 -------
+I am not at my desk, so I can't do any debugging yet, but....
+
+Inside the method
+
+ Container_Class::destroy_callback(GtkObject* self)
+
+I see the following statement
+
+ if(cppChild && !cppChild->is_managed_())
+
+And in my previous comments I was showing that the GTk::VBox is
+managed object of the (Singleton?)Gtk::VBox_Class
+
+Might that be a problem?
--__--__--
Message: 8
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, szombath bifab de
Cc:
Date: Wed, 25 Jun 2003 05:59:09 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 91404] Changed - Gtk::Button: memory leak when using mnemonic=true.
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=91404
Changed by murrayc usa net
--- shadow/91404 Sun Sep 15 12:45:04 2002
+++ shadow/91404.tmp.18991 Wed Jun 25 05:59:09 2003
@@ -83,6 +83,16 @@
properly. gtk_widget_destroy() will always succeed, but
gtk_container_remove() isn't guarranteed to cause destruction.
It is now clear that this callback was necessary, not just as a
refcount hack - we really do need to remove non-manage()ed
widgets, because SINKing them does not prevent them from being
destroyed in gtk_container_destroy().
+
+------- Additional Comments From murrayc usa net 2003-06-25 05:59 -------
+I don't think so. The whole point of that code is explained in the
+comment at the start of the method:
+// We need to remove non-manage()ed widgets to prevent
+gtk_container_destroy() from destroying them.
+// Contary to what we thought once, even non-floating (sunk) widgets
+are destroyed by gtk_container_destroy()
+
+It should have no effect on manage()s widgets.
--__--__--
Message: 9
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, szombath bifab de
Cc:
Date: Wed, 25 Jun 2003 05:59:35 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 91404] Changed - Gtk::Button: memory leak when using mnemonic=true.
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=91404
Changed by murrayc usa net
--- shadow/91404 Wed Jun 25 05:59:09 2003
+++ shadow/91404.tmp.19057 Wed Jun 25 05:59:35 2003
@@ -93,6 +93,9 @@
// We need to remove non-manage()ed widgets to prevent
gtk_container_destroy() from destroying them.
// Contary to what we thought once, even non-floating (sunk) widgets
are destroyed by gtk_container_destroy()
It should have no effect on manage()s widgets.
+
+------- Additional Comments From murrayc usa net 2003-06-25 05:59 -------
+Sorry, ignore that. Wrong bug.
--__--__--
Message: 10
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
harald hopfes hopfes sysde eads net
Cc:
Date: Wed, 25 Jun 2003 06:00:05 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=114568
Changed by murrayc usa net
--- shadow/114568 Wed Jun 25 05:50:49 2003
+++ shadow/114568.tmp.19580 Wed Jun 25 06:00:05 2003
@@ -1133,6 +1133,16 @@
if(cppChild && !cppChild->is_managed_())
And in my previous comments I was showing that the GTk::VBox is
managed object of the (Singleton?)Gtk::VBox_Class
Might that be a problem?
+
+------- Additional Comments From murrayc usa net 2003-06-25 06:00 -------
+I don't think so. The whole point of that code is explained in the
+comment at the start of the method:
+// We need to remove non-manage()ed widgets to prevent
+gtk_container_destroy() from destroying them.
+// Contary to what we thought once, even non-floating (sunk) widgets
+are destroyed by gtk_container_destroy()
+
+It should have no effect on manage()ed widgets
--__--__--
Message: 11
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
harald hopfes hopfes sysde eads net
Cc: murrayc usa net
Date: Wed, 25 Jun 2003 12:23:50 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=114568
Changed by harald hopfes hopfes sysde eads net
--- shadow/114568 Wed Jun 25 06:00:05 2003
+++ shadow/114568.tmp.10175 Wed Jun 25 12:23:50 2003
@@ -1143,6 +1143,21 @@
// We need to remove non-manage()ed widgets to prevent
gtk_container_destroy() from destroying them.
// Contary to what we thought once, even non-floating (sunk) widgets
are destroyed by gtk_container_destroy()
It should have no effect on manage()ed widgets
+
+------- Additional Comments From harald hopfes hopfes sysde eads net 2003-06-25 12:23 -------
+Here is the updated oder of events:
+(including the "dispose")
+
+ gtk_widget_destroy: GtkVBox
+ gtk_object_destroy: GtkVBox
+ gtk_object_dispose: GtkVBox
+ gtk_object_dispose: GtkVBox calling gtk_signal_emit
+ ** (main:26364): WARNING **: on_vbox_destroyed
+ ** (main:26364): WARNING **: Data of GtkVBox: refcount: 3
+ gtk_container_destroy: GtkVBox
+ gtk_widget_real_destroy: GtkVBox
+ gtk_object_real_destroy: GtkVBox
+
--__--__--
Message: 12
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
harald hopfes hopfes sysde eads net
Cc: murrayc usa net
Date: Wed, 25 Jun 2003 12:37:01 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=114568
Changed by harald hopfes hopfes sysde eads net
--- shadow/114568 Wed Jun 25 12:23:50 2003
+++ shadow/114568.tmp.15621 Wed Jun 25 12:37:01 2003
@@ -1158,6 +1158,11 @@
** (main:26364): WARNING **: on_vbox_destroyed
** (main:26364): WARNING **: Data of GtkVBox: refcount: 3
gtk_container_destroy: GtkVBox
gtk_widget_real_destroy: GtkVBox
gtk_object_real_destroy: GtkVBox
+
+------- Additional Comments From harald hopfes hopfes sysde eads net 2003-06-25 12:37 -------
+Created an attachment (id=17759)
+g_object_qdata_out.txt
+
--__--__--
Message: 13
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
harald hopfes hopfes sysde eads net
Cc:
Date: Wed, 25 Jun 2003 13:11:54 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=114568
Changed by murrayc usa net
--- shadow/114568 Wed Jun 25 12:58:16 2003
+++ shadow/114568.tmp.30497 Wed Jun 25 13:11:54 2003
@@ -1211,6 +1211,19 @@
g_signal_connect(G_OBJECT(vbo), "destroy",
G_CALLBACK(on_vbox_destroyed), 0);
as this one is really called by the "gtk_object_dispose"
+
+------- Additional Comments From murrayc usa net 2003-06-25 13:11 -------
+You have done a lot of good work here and it will help me to find the
+bug. Well done and thank you. I'll try to find some time this evening.
+
+Yes, deleting a C++ instance that has no underlying C instance should
+work, but I've never tried it because it should never be possible.
+
+Well, if you delete it now then it will be double-delete when I fix
+the bug. I'm interested, in what kind of application is the occasional
+leak based on GUI interaction such a critical problem?
+
+re. dispose: Maybe. I will investigate. It has worked so far elsewhere.
--__--__--
Message: 14
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
harald hopfes hopfes sysde eads net
Cc: murrayc usa net
Date: Wed, 25 Jun 2003 12:49:01 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=114568
Changed by harald hopfes hopfes sysde eads net
--- shadow/114568 Wed Jun 25 12:37:01 2003
+++ shadow/114568.tmp.20729 Wed Jun 25 12:49:00 2003
@@ -1163,6 +1163,27 @@
------- Additional Comments From harald hopfes hopfes sysde eads net 2003-06-25 12:37 -------
Created an attachment (id=17759)
g_object_qdata_out.txt
+
+------- Additional Comments From harald hopfes hopfes sysde eads net 2003-06-25 12:48 -------
+I find the place where the signals for
+
+ g_signal_connect(G_OBJECT(vbo), "destroy",
+ G_CALLBACK(on_vbox_destroyed), 0);
+
+of my test program is emitted, but I have no clue
+where the signal (?? is it one) for
+
+ g_object_set_qdata_full(object, Glib::quark_, this,
+ &destroy_notify_callback_);
+
+is emitted?
+
+Somewhere should be a g_object_get_qdata(Glib::quark_) and some lines
+later a function call to the return value of g_object_get_qdata
+
+But as Glib::quark_ is only defined inside GTKMM how should it be
+possible that the callback is triggered from GTK+?
+
--__--__--
Message: 15
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
harald hopfes hopfes sysde eads net
Cc: murrayc usa net
Date: Wed, 25 Jun 2003 12:51:53 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=114568
Changed by harald hopfes hopfes sysde eads net
--- shadow/114568 Wed Jun 25 12:49:00 2003
+++ shadow/114568.tmp.22120 Wed Jun 25 12:51:53 2003
@@ -1184,6 +1184,16 @@
Somewhere should be a g_object_get_qdata(Glib::quark_) and some lines
later a function call to the return value of g_object_get_qdata
But as Glib::quark_ is only defined inside GTKMM how should it be
possible that the callback is triggered from GTK+?
+
+------- Additional Comments From harald hopfes hopfes sysde eads net 2003-06-25 12:51 -------
+What happens if I explicitly delete the Gtk::VBox wrapper of the
+GtkVBox if the GtkVBox is already deleted?
+
+Should work, shouldn't it?
+
+I am not so deep into the GTKMM or GTK+ stuff that I will be able to
+find the bug, so I think it is better if I delete the Gtk::VBox
+myself.
--__--__--
Message: 16
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
harald hopfes hopfes sysde eads net
Cc: murrayc usa net
Date: Wed, 25 Jun 2003 12:58:16 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=114568
Changed by harald hopfes hopfes sysde eads net
--- shadow/114568 Wed Jun 25 12:51:53 2003
+++ shadow/114568.tmp.24796 Wed Jun 25 12:58:16 2003
@@ -1194,6 +1194,23 @@
Should work, shouldn't it?
I am not so deep into the GTKMM or GTK+ stuff that I will be able to
find the bug, so I think it is better if I delete the Gtk::VBox
myself.
+
+------- Additional Comments From harald hopfes hopfes sysde eads net 2003-06-25 12:58 -------
+Just a last thought:
+Maybe
+
+ g_object_set_qdata_full(object,
+ Glib::quark_,
+ this, &destroy_notify_callback_);
+ inside ObjectBase::_set_current_wrapper
+
+should be replaced with
+
+ g_signal_connect(G_OBJECT(vbo), "destroy",
+ G_CALLBACK(on_vbox_destroyed), 0);
+
+as this one is really called by the "gtk_object_dispose"
+
--__--__--
_______________________________________________
Gtkmm-forge mailing list
Gtkmm-forge lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
End of Gtkmm-forge Digest
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]