Send Gtkmm-forge mailing list submissions to
[EMAIL PROTECTED]
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
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
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. Do not try to unsubscribe gtkmm-forge from gtkmm-list.
Today's Topics:
1. [Bug 168268] 0 should be NULL in one gtk call ([EMAIL PROTECTED])
2. [Bug 168268] 0 should be NULL in one gtk call ([EMAIL PROTECTED])
3. [Bug 154004] Values above VScale widgets from a Glade UI disappear when
the widget is used ([EMAIL PROTECTED])
4. [Bug 154004] Values above VScale widgets from a Glade UI disappear when
the widget is used ([EMAIL PROTECTED])
5. [Bug 168268] 0 should be NULL in one gtk call ([EMAIL PROTECTED])
--__--__--
Message: 1
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc:
Date: Thu, 24 Feb 2005 04:53:26 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 168268] 0 should be NULL in one gtk call
Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.
http://bugzilla.gnome.org/show_bug.cgi?id=168268
gtkmm | build | Ver: 2.2
------- Additional Comments From Murray Cumming 2005-02-24 04:53 -------
Does this cause a build error? Why do you need this? Please remember to patch
the ChangeLog in future.
------- You are receiving this mail because: -------
You are the assignee for the bug.
--__--__--
Message: 2
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc:
Date: Thu, 24 Feb 2005 05:01:50 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 168268] 0 should be NULL in one gtk call
Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.
http://bugzilla.gnome.org/show_bug.cgi?id=168268
gtkmm | build | Ver: 2.2
------- Additional Comments From [EMAIL PROTECTED] 2005-02-24 05:01 -------
no, just a warning with gcc4 and annotated gtk2 headers.
It might break on runtime on 64bit systems.
------- You are receiving this mail because: -------
You are the assignee for the bug.
--__--__--
Message: 3
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc:
Date: Thu, 24 Feb 2005 05:19:17 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 154004] Values above VScale widgets from a Glade
UI disappear when the widget is used
Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.
http://bugzilla.gnome.org/show_bug.cgi?id=154004
gnomemm | libglademm | Ver: 2.4
------- Additional Comments From Michael Hofmann 2005-02-24 05:19 -------
I got it fixed for C++. There the bug is caused by the C++ wrapper using
Glib::ustrings, which do not understand the concept of NULL.
To format a value, a signal is emmited. single_string_accumulator
(gtkscale.c:114) is used to decide whether more handler need to be called. It
evaluates the return value (the formatted text) of the previus handler for NULL
and if not, goes on calling more handlers if available.
This works fine as long as there is no C++ wrapper around. With the wrapper, it
goes sth. like this (I'm a little bit confused by the code of who calls who, so
it may be slightly different):
emit: expects gchar*, NULL value breaks
Scale_Class::format_value_callback: returns gchar*
class::on_format_value:: returns Glib::ustring
calls C format_value method: returns gchar*
Because the last C function returns NULL which is converted to Glib::ustring("")
which is converted back to a gchar*("") which is not NULL this breaks the
system.
The default action in _gtk_scale_format_value (gtkscale.c:636) is never executed
because it expects NULL when nobody else has a better way to convert, which is
not possible because single_string_accumulator returns an empty string, which it
regards as a value, not NULL, although there is nobody handling it.
This also breaks overwriting the on_format_value method in the wrapper, because
it gets never executed, because single_string_accumulator breaks after it got an
empty string from the default handler.
A first patch looks may look like this:
--- gtkscale.c.orig 2004-08-09 19:59:52.000000000 +0300
+++ gtkscale.c 2005-02-24 11:50:05.000000000 +0200
@@ -121,6 +121,8 @@
const gchar *str;
str = g_value_get_string (handler_return);
+ if (str != NULL && str[0] == 0)
+ str = NULL;
g_value_set_string (return_accu, str);
continue_emission = str == NULL;
This patches single_string_accumulator to react on empty strings in the same way
like on NULL. I don't know whether other wrappers are affected, maybe this
should be handled there.
Sorry for the confusing text, I'm not used to programming raw Gtk+.
------- You are receiving this mail because: -------
You are the assignee for the bug.
--__--__--
Message: 4
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc:
Date: Thu, 24 Feb 2005 05:19:54 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 154004] Values above VScale widgets from a Glade
UI disappear when the widget is used
Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.
http://bugzilla.gnome.org/show_bug.cgi?id=154004
gnomemm | libglademm | Ver: 2.4
Michael Hofmann changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
------- You are receiving this mail because: -------
You are the assignee for the bug.
--__--__--
Message: 5
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc:
Date: Thu, 24 Feb 2005 14:00:20 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 168268] 0 should be NULL in one gtk call
Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.
http://bugzilla.gnome.org/show_bug.cgi?id=168268
gtkmm | build | Ver: 2.2
------- Additional Comments From Murray Cumming 2005-02-24 14:00 -------
Could you show us the warning please? What do you mean by "annotated" gtk2
headers?
In general we use 0 for null pointers all over gtkmm. It's kind of a C++ thing.
------- You are receiving this mail because: -------
You are the assignee for the bug.
--__--__--
_______________________________________________
Gtkmm-forge mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
End of Gtkmm-forge Digest
_______________________________________________
gtkmm-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gtkmm-list
