GNOME.org
 

[gtkmm] Gtkmm-forge digest, Vol 1 #224 - 6 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 92514] Changed - pangomm has some bugs and incomplete documentation (bugzilla-daemon widget gnome org)
   2. [Bug 63768] Changed - Can't instantiate a GtkTreeStore with just g_object_new() (bugzilla-daemon widget gnome org)
   3. [Bug 92514] Changed - pangomm has some bugs and incomplete documentation (bugzilla-daemon widget gnome org)
   4. [Bug 92514] Changed - pangomm has some bugs and incomplete documentation (bugzilla-daemon widget gnome org)
   5. [Bug 92208] Changed - Unable to inherit from items (bugzilla-daemon widget gnome org)
   6. [Bug 92514] Changed - pangomm has some bugs and incomplete documentation (bugzilla-daemon widget gnome org)

--__--__--

Message: 1
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, MHL Schulze t-online de
Cc: 
Date: Tue, 10 Sep 2002 15:40:00 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 92514] Changed - pangomm has some bugs and incomplete documentation

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

Changed by murrayc usa net 

--- shadow/92514	Tue Sep 10 11:40:16 2002
+++ shadow/92514.tmp.6308	Tue Sep 10 15:40:00 2002
@@ -145,6 +145,13 @@
 - Color::parse() takes a std::string: the color names are the ones
 used by X11 and I don't expect those to be UTF-8 in the future.
 - The internal string representation of a Language has RFC-3066
 format. I haven't read http://www.faqs.org/rfcs/rfc3066.html in detail
 but a quick look didn't give any hints about the usage of UTF strings
 for language tags which wouldn't make much sense to me anyway.
+
+------- Additional Comments From murrayc usa net  2002-09-10 15:39 -------
+If you aren't _certain_ that something will never be UTF8, then it
+must use Glib::ustring. Don't impose constraints if you are not sure.
+It's easy to give a std::string to a Glib::ustring, but it's a
+theoreticaL loss of data to give a Glib::ustring to a std::string.
+



--__--__--

Message: 2
From: bugzilla-daemon widget gnome org
To: gtktreeview-bugs gtk org
Cc: gtkmm-forge lists sourceforge net
Date: Tue, 10 Sep 2002 15:42:36 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 63768] Changed - Can't instantiate a GtkTreeStore with just g_object_new()

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

Changed by murrayc usa net 

--- shadow/63768	Tue Sep 10 07:34:45 2002
+++ shadow/63768.tmp.6821	Tue Sep 10 15:42:36 2002
@@ -9,13 +9,12 @@
 Priority: Normal
 Component: GtkTreeView
 AssignedTo: gtktreeview-bugs gtk org                            
 ReportedBy: murrayc usa net               
 TargetMilestone: future
 URL: 
-Cc: gtkmm-forge lists sourceforge net
 Summary: Can't instantiate a GtkTreeStore with just g_object_new()
 OtherBugsDependingOnThis: 86865
 
 *_new() functions should be just convenience wrappers, but there doesn't
 seem to be a way to instantiate a GtkTreeStore with only g_object_new() as
 there are no construct-time properties to correspond to the number of



--__--__--

Message: 3
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Tue, 10 Sep 2002 17:24:51 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 92514] Changed - pangomm has some bugs and incomplete documentation

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

Changed by mhl schulze t-online de 

--- shadow/92514	Tue Sep 10 15:40:00 2002
+++ shadow/92514.tmp.963	Tue Sep 10 17:24:51 2002
@@ -152,6 +152,11 @@
 ------- Additional Comments From murrayc usa net  2002-09-10 15:39 -------
 If you aren't _certain_ that something will never be UTF8, then it
 must use Glib::ustring. Don't impose constraints if you are not sure.
 It's easy to give a std::string to a Glib::ustring, but it's a
 theoreticaL loss of data to give a Glib::ustring to a std::string.
 
+
+------- Additional Comments From MHL Schulze t-online de  2002-09-10 17:24 -------
+Okay, then Attribute::register_type() will get a Glib::ustring
+argument. The other two certainly won't ever be UTF-8. I will make the
+patch tomorrow (if anoncvs is in sync by then...).



--__--__--

Message: 4
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, MHL Schulze t-online de
Cc: 
Date: Wed, 11 Sep 2002 03:02:35 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 92514] Changed - pangomm has some bugs and incomplete documentation

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

Changed by murrayc usa net 

--- shadow/92514	Tue Sep 10 17:24:51 2002
+++ shadow/92514.tmp.18575	Wed Sep 11 03:02:35 2002
@@ -157,6 +157,11 @@
 
 
 ------- Additional Comments From MHL Schulze t-online de  2002-09-10 17:24 -------
 Okay, then Attribute::register_type() will get a Glib::ustring
 argument. The other two certainly won't ever be UTF-8. I will make the
 patch tomorrow (if anoncvs is in sync by then...).
+
+------- Additional Comments From murrayc usa net  2002-09-11 03:02 -------
+Are you 100% certain that things such as the X11 colour can not be
+UTF8?   If you have not looked at the specification recently then I
+don't think that you can be 100% certain.



--__--__--

Message: 5
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, indigo sempiternity org
Cc: 
Date: Wed, 11 Sep 2002 03:44:50 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 92208] Changed - Unable to inherit from items

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

Changed by murrayc usa net 

--- shadow/92208	Wed Sep  4 22:45:16 2002
+++ shadow/92208.tmp.23689	Wed Sep 11 03:44:50 2002
@@ -61,6 +61,32 @@
 
 As for a fix for the problem, I can't think of any workaround. Damn
 gcc sucks... Perhaps if someone could point me towards the specific
 dynamic_cast that's causing the problem I could rewrite it with static
 casts? I can't really require gcc 3.2, and I can't avoid inheriting
 without major troubles, so any ideas would be much apreciated :)
+
+------- Additional Comments From murrayc usa net  2002-09-11 03:44 -------
+I have looked the Gnome::Canvas::Text class that you use in your
+example code. There is an alternative constructor. You could then just
+set the properties in your own constructor. That's what the other
+constructor does anyway (though you should use property_*.set_value()
+rather than set(...)).
+
+As long as these workarounds exist then I think I don't think this is
+critical, even though I use the same broken compiler.
+
+As for dynamic_cast<>, it's in the singal callbacks. You should see it
+in the backtrace. It's generated by tools/m4/signal.m4. I can't
+remember exactly why we use it - I seem to remember that it was the
+only way (or most convenient way) to cast when using multiple
+inheritance with virtual base classes. It would be nice to
+double-check that and add more comments if possible.
+
+That .m4 file currently has this comment, but it doesn't make perfect
+sense to me now:
+
+dnl We have to use a dynamic_cast because we do not 
+dnl  know the actual type from which to cast up.
+  CppObjectType *const obj = dynamic_cast<CppObjectType*>(
+      Glib::ObjectBase::_get_current_wrapper`'((GObject*)$8));
+



--__--__--

Message: 6
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Wed, 11 Sep 2002 14:58:52 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 92514] Changed - pangomm has some bugs and incomplete documentation

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

Changed by mhl schulze t-online de 

--- shadow/92514	Wed Sep 11 03:02:35 2002
+++ shadow/92514.tmp.30826	Wed Sep 11 14:58:52 2002
@@ -162,6 +162,15 @@
 patch tomorrow (if anoncvs is in sync by then...).
 
 ------- Additional Comments From murrayc usa net  2002-09-11 03:02 -------
 Are you 100% certain that things such as the X11 colour can not be
 UTF8?   If you have not looked at the specification recently then I
 don't think that you can be 100% certain.
+
+------- Additional Comments From MHL Schulze t-online de  2002-09-11 14:58 -------
+The "specification" in the form of the man-page of the program "rgb"
+that I found doesn't mention anything about the string format of the
+color names. Currently, all names are english even in my german
+distribution. Obviously we cannot be 100% sure that this is the case
+for  future releases and I don't see how a Glib::ustring could hurt
+here. So I'll change the parameter of Color::parse() to Glib::ustring,
+too. (This seems to be along your line of argumentation :)




--__--__--

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