GNOME.org
 

[gtkmm] Gtkmm-forge digest, Vol 1 #233 - 13 msgs

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 93694] New - Glib::Dispatcher and arbitrary MainContext (bugzilla-daemon widget gnome org)
   2. [Bug 93694] Changed - Glib::Dispatcher and arbitrary MainContext (bugzilla-daemon widget gnome org)
   3. [Bug 93703] New - Gtk-CRITICAL on Dialog destruction (bugzilla-daemon widget gnome org)
   4. [Bug 93585] Changed - IOChannel wrappers for glibmm (bugzilla-daemon widget gnome org)
   5. [Bug 93585] Changed - IOChannel wrappers for glibmm (bugzilla-daemon widget gnome org)
   6. [Bug 93694] Changed - Glib::Dispatcher and arbitrary MainContext (bugzilla-daemon widget gnome org)
   7. [Bug 93694] Changed - Glib::Dispatcher and arbitrary MainContext (bugzilla-daemon widget gnome org)
   8. [Bug 93703] Changed - Gtk-CRITICAL on Dialog destruction (bugzilla-daemon widget gnome org)
   9. [Bug 93703] Changed - Gtk-CRITICAL on Dialog destruction (bugzilla-daemon widget gnome org)
  10. [Bug 93694] Changed - Glib::Dispatcher and arbitrary MainContext (bugzilla-daemon widget gnome org)
  11. [Bug 91410] Changed - Gtk::Menu: possible memory leak. (bugzilla-daemon widget gnome org)
  12. [Bug 93694] Changed - Glib::Dispatcher and arbitrary MainContext (bugzilla-daemon widget gnome org)
  13. [Bug 93787] New - Exception what()s are in locale encoding, not UTF-8 (bugzilla-daemon widget gnome org)

--__--__--

Message: 1
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Thu, 19 Sep 2002 15:37:06 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 93694] New - Glib::Dispatcher and arbitrary MainContext

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=93694

Changed by puchs ap univie ac at 

--- shadow/93694	Thu Sep 19 15:37:06 2002
+++ shadow/93694.tmp.25746	Thu Sep 19 15:37:06 2002
@@ -0,0 +1,21 @@
+Bug#: 93694
+Product: gtkmm
+Version: 2.0
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: enhancement
+Priority: Normal
+Component: general
+AssignedTo: gtkmm-forge lists sourceforge net                            
+ReportedBy: puchs ap univie ac at               
+TargetMilestone: ---
+URL: 
+Summary: Glib::Dispatcher and arbitrary MainContext
+
+The signal in the DispatcherNotifier connect only to the default
+MainContext. The proposed enhancement offers the possibility to 
+use an arbitrary MainContext.The patch adds an additional constructor
+to Glib::Dispatcher, that accepts a reference to Glib::RefPtr<MainContext>
+an connects the DispatcherNotifier signal to that context.



--__--__--

Message: 2
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Thu, 19 Sep 2002 15:38:30 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 93694] Changed - Glib::Dispatcher and arbitrary MainContext

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=93694

Changed by puchs ap univie ac at 

--- shadow/93694	Thu Sep 19 15:37:06 2002
+++ shadow/93694.tmp.25975	Thu Sep 19 15:38:30 2002
@@ -16,6 +16,11 @@
 
 The signal in the DispatcherNotifier connect only to the default
 MainContext. The proposed enhancement offers the possibility to 
 use an arbitrary MainContext.The patch adds an additional constructor
 to Glib::Dispatcher, that accepts a reference to Glib::RefPtr<MainContext>
 an connects the DispatcherNotifier signal to that context.
+
+------- Additional Comments From puchs ap univie ac at  2002-09-19 15:38 -------
+Created an attachment (id=11174)
+the patch adds the possibility to use an arbitrary MainContext
+



--__--__--

Message: 3
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Thu, 19 Sep 2002 17:08:07 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 93703] New - Gtk-CRITICAL on Dialog destruction

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=93703

Changed by dss home se 

--- shadow/93703	Thu Sep 19 17:08:07 2002
+++ shadow/93703.tmp.19140	Thu Sep 19 17:08:07 2002
@@ -0,0 +1,54 @@
+Bug#: 93703
+Product: gtkmm
+Version: 2.0
+OS: Linux
+OS Details: RedHat LInux 7.3
+Status: NEW   
+Resolution: 
+Severity: minor
+Priority: Normal
+Component: general
+AssignedTo: gtkmm-forge lists sourceforge net                            
+ReportedBy: dss home se               
+TargetMilestone: ---
+URL: 
+Summary: Gtk-CRITICAL on Dialog destruction
+
+When you close the dialog in the following example i get an error message
+in the console:
+
+[sumpan e dialog_entry_test]$ ./dialog_entry_test 
+
+(dialog_entry_test:17708): Gtk-CRITICAL **: file gtkcontainer.c: line 878
+(gtk_container_remove): assertion `GTK_IS_CONTAINER (container)' failed
+
+
+Is there a problem placing a Gtk::Box inside another Gtk::Box? If you
+change the entry to a pointer and use manage to initialize it everything
+works as expected....
+
+---
+#include <gtkmm.h>
+
+using namespace SigC;
+
+class TestDialog : public Gtk::Dialog
+{
+public:
+  TestDialog() : Gtk::Dialog("Test-dialog", true, true) {
+    get_vbox()->pack_start(vbox);
+    vbox.pack_start(e);
+    show_all();
+  }
+private:
+  Gtk::Entry e;
+  Gtk::VBox vbox;
+};
+
+int main (int argc, char *argv[])
+{
+  Gtk::Main kit(argc, argv);
+  TestDialog d;
+  kit.run(d);
+  return 0;
+}



--__--__--

Message: 4
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Thu, 19 Sep 2002 17:33:29 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 93585] Changed - IOChannel wrappers for glibmm

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=93585

Changed by abas aix meng auth gr 

--- shadow/93585	Thu Sep 19 12:56:00 2002
+++ shadow/93585.tmp.22427	Thu Sep 19 17:33:29 2002
@@ -48,6 +48,11 @@
 * Please remove the flippant comments such as "Oh, Lord, please 
 forgive me." They are not helpful.
 * A cvs diff might be better, if possible.
 
 Otherwise, well done. It probably wasn't easy to figure out how the 
 gtkmmproc macros can be used.
+
+------- Additional Comments From abas aix meng auth gr  2002-09-19 17:33 -------
+Created an attachment (id=11176)
+iochannel.patch
+



--__--__--

Message: 5
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Thu, 19 Sep 2002 17:35:41 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 93585] Changed - IOChannel wrappers for glibmm

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=93585

Changed by abas aix meng auth gr 

--- shadow/93585	Thu Sep 19 17:33:29 2002
+++ shadow/93585.tmp.22790	Thu Sep 19 17:35:41 2002
@@ -53,6 +53,10 @@
 gtkmmproc macros can be used.
 
 ------- Additional Comments From abas aix meng auth gr  2002-09-19 17:33 -------
 Created an attachment (id=11176)
 iochannel.patch
 
+
+------- Additional Comments From abas aix meng auth gr  2002-09-19 17:35 -------
+This should be a more proper patch. Includes ChangeLog entry,
+basic documentation and a better iostream-IOChannel.



--__--__--

Message: 6
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, puchs ap univie ac at
Cc: 
Date: Fri, 20 Sep 2002 04:04:16 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 93694] Changed - Glib::Dispatcher and arbitrary MainContext

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=93694

Changed by murrayc usa net 

--- shadow/93694	Thu Sep 19 15:38:30 2002
+++ shadow/93694.tmp.13735	Fri Sep 20 04:04:16 2002
@@ -21,6 +21,11 @@
 an connects the DispatcherNotifier signal to that context.
 
 ------- Additional Comments From puchs ap univie ac at  2002-09-19 15:38 -------
 Created an attachment (id=11174)
 the patch adds the possibility to use an arbitrary MainContext
 
+
+------- Additional Comments From murrayc usa net  2002-09-20 04:04 -------
+I think the constructor should be marked "explicit".
+
+I think Daniel Elstner needs to approve this patch.



--__--__--

Message: 7
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Fri, 20 Sep 2002 04:19:43 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 93694] Changed - Glib::Dispatcher and arbitrary MainContext

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=93694

Changed by puchs ap univie ac at 

--- shadow/93694	Fri Sep 20 04:04:16 2002
+++ shadow/93694.tmp.15609	Fri Sep 20 04:19:42 2002
@@ -26,6 +26,16 @@
 
 
 ------- Additional Comments From murrayc usa net  2002-09-20 04:04 -------
 I think the constructor should be marked "explicit".
 
 I think Daniel Elstner needs to approve this patch.
+
+------- Additional Comments From puchs ap univie ac at  2002-09-20 04:19 -------
+You are right. Making it "explicit" would be better. Sorry, that I did 
+not do it.
+
+As a test for the patch I modified Daniel Elstner's dispatcher example.
+The modified version contains 2 mainloops which a dispatcher signal in
+each direction. It worked with no obvious problems. I may of course
+have overlooked something. Is there any interest for an additional
+dispatcher example if this patch is accepted? 



--__--__--

Message: 8
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, dss home se
Cc: 
Date: Fri, 20 Sep 2002 04:21:06 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 93703] Changed - Gtk-CRITICAL on Dialog destruction

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=93703

Changed by murrayc usa net 

--- shadow/93703	Thu Sep 19 17:08:07 2002
+++ shadow/93703.tmp.15949	Fri Sep 20 04:21:06 2002
@@ -1,12 +1,12 @@
 Bug#: 93703
 Product: gtkmm
 Version: 2.0
 OS: Linux
 OS Details: RedHat LInux 7.3
-Status: NEW   
+Status: ASSIGNED   
 Resolution: 
 Severity: minor
 Priority: Normal
 Component: general
 AssignedTo: gtkmm-forge lists sourceforge net                            
 ReportedBy: dss home se               
@@ -49,6 +49,9 @@
 {
   Gtk::Main kit(argc, argv);
   TestDialog d;
   kit.run(d);
   return 0;
 }
+
+------- Additional Comments From murrayc usa net  2002-09-20 04:21 -------
+Confirmed. I added this code to gtkmm/tests/dialog/.



--__--__--

Message: 9
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, dss home se
Cc: 
Date: Fri, 20 Sep 2002 06:26:33 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 93703] Changed - Gtk-CRITICAL on Dialog destruction

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=93703

Changed by murrayc usa net 

--- shadow/93703	Fri Sep 20 04:21:06 2002
+++ shadow/93703.tmp.30893	Fri Sep 20 06:26:33 2002
@@ -1,13 +1,13 @@
 Bug#: 93703
 Product: gtkmm
 Version: 2.0
 OS: Linux
 OS Details: RedHat LInux 7.3
-Status: ASSIGNED   
-Resolution: 
+Status: RESOLVED   
+Resolution: FIXED
 Severity: minor
 Priority: Normal
 Component: general
 AssignedTo: gtkmm-forge lists sourceforge net                            
 ReportedBy: dss home se               
 TargetMilestone: ---
@@ -52,6 +52,17 @@
   kit.run(d);
   return 0;
 }
 
 ------- Additional Comments From murrayc usa net  2002-09-20 04:21 -------
 Confirmed. I added this code to gtkmm/tests/dialog/.
+
+------- Additional Comments From murrayc usa net  2002-09-20 06:26 -------
+I think I fixed this. Please check cvs (when anoncvs syncs) and reopen
+if it's still a problem:
+
+2002-09-20  Murray Cumming  <murrayc usa net>
+
+	* gtk/src/object.ccg: Container_Class::destroy_callback():
+	Added a g_object_ref before the gtk_container_remove for
+	un-manage()ed child widgets, so that they are not destroyed before
+	their C++ destructors destroy them with gtk_object_destroy().



--__--__--

Message: 10
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, puchs ap univie ac at
Cc: 
Date: Fri, 20 Sep 2002 10:28:24 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 93694] Changed - Glib::Dispatcher and arbitrary MainContext

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=93694

Changed by murrayc usa net 

--- shadow/93694	Fri Sep 20 04:19:42 2002
+++ shadow/93694.tmp.28936	Fri Sep 20 10:28:24 2002
@@ -36,6 +36,9 @@
 
 As a test for the patch I modified Daniel Elstner's dispatcher example.
 The modified version contains 2 mainloops which a dispatcher signal in
 each direction. It worked with no obvious problems. I may of course
 have overlooked something. Is there any interest for an additional
 dispatcher example if this patch is accepted? 
+
+------- Additional Comments From murrayc usa net  2002-09-20 10:28 -------
+Yes, an example would probably be helpful.



--__--__--

Message: 11
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, szombath bifab de
Cc: 
Date: Fri, 20 Sep 2002 10:30:02 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 91410] Changed - Gtk::Menu: possible memory leak.

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=91410

Changed by murrayc usa net 

--- shadow/91410	Tue Sep 17 03:55:22 2002
+++ shadow/91410.tmp.29037	Fri Sep 20 10:30:01 2002
@@ -9,13 +9,13 @@
 Priority: Normal
 Component: general
 AssignedTo: gtkmm-forge lists sourceforge net                            
 ReportedBy: szombath bifab de               
 TargetMilestone: ---
 URL: 
-Summary: Gtk::Menu not properly C++ wrapped
+Summary: Gtk::Menu: possible memory leak.
 
 Detected by purify, we think that Gtk::Menu objects are not properly
 registered. It occurs as a GtkWindow.
 
 As an aftereffect we see for instance that Gtk::Window::list_toplevels
 produces a memory leak with Gtk::Menu objects, because



--__--__--

Message: 12
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Fri, 20 Sep 2002 10:46:56 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 93694] Changed - Glib::Dispatcher and arbitrary MainContext

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=93694

Changed by puchs ap univie ac at 

--- shadow/93694	Fri Sep 20 10:28:24 2002
+++ shadow/93694.tmp.31268	Fri Sep 20 10:46:56 2002
@@ -39,6 +39,10 @@
 each direction. It worked with no obvious problems. I may of course
 have overlooked something. Is there any interest for an additional
 dispatcher example if this patch is accepted? 
 
 ------- Additional Comments From murrayc usa net  2002-09-20 10:28 -------
 Yes, an example would probably be helpful.
+
+------- Additional Comments From puchs ap univie ac at  2002-09-20 10:46 -------
+I will clean up and comment the example tomorrow and attach it to this
+bug as another patch against the cvs tree.



--__--__--

Message: 13
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Fri, 20 Sep 2002 13:43:09 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 93787] New - Exception what()s are in locale encoding, not UTF-8

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=93787

Changed by olau hardworking dk 

--- shadow/93787	Fri Sep 20 13:43:09 2002
+++ shadow/93787.tmp.21254	Fri Sep 20 13:43:09 2002
@@ -0,0 +1,35 @@
+Bug#: 93787
+Product: gtkmm
+Version: 2.0
+OS: other
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: normal
+Priority: Normal
+Component: general
+AssignedTo: gtkmm-forge lists sourceforge net                            
+ReportedBy: olau hardworking dk               
+TargetMilestone: ---
+URL: 
+Summary: Exception what()s are in locale encoding, not UTF-8
+
+This results in problems with displaying the error in a user-friendly way
+(i.e. using a message dialog instead of just outputting to a perhaps
+non-existing terminal). For instance, catching a Glib::Error and
+concatenating the return value of the what() member with some extra
+information will usually not give a proper UTF-8 ustring when either GTK+
+or the program is i18nized.
+
+Perhaps GTK+ converts the messages as a convenience - all the examples I
+could find in the documentation simply display the error with
+fprintf(stderr, ...). However, the conversion results in surprising
+behaviour that is undetectable unless running in an i18nized environment.
+And displaying critical errors in the terminal is _really_ unfriendly.
+
+So if not too much Gtkmm application code depends on the format of the
+what() messages (I guess this is the case for GTK+ itself), I propose
+undoing the conversion in the wrapper with locale_to_utf8.
+
+Else, at least it badly needs documenting. But I won't provide a patch
+before a decision is made. :-)




--__--__--

_______________________________________________
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]