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 588989] optional flag in Glib::OptionEntry cause crash
is the arg is omitted (glibmm (bugzilla.gnome.org))
2. [Bug 558017] Build failure due to some perl macro
(gtkmm (bugzilla.gnome.org))
3. [Bug 573482] Gtk::Builder: autoconnecting signals
(gtkmm (bugzilla.gnome.org))
4. [Bug 573482] Gtk::Builder: autoconnecting signals
(gtkmm (bugzilla.gnome.org))
5. [Bug 574530] gtkmm-documentation: html should not rebuild
when building the tarball. (gtkmm (bugzilla.gnome.org))
6. [Bug 574935] win32: gtk_window_set_geometry_hints() has no
effect until the window is moved (gtk+ (bugzilla.gnome.org))
7. [Bug 553024] switching notebook pages while removing them
fails ungracefully (gtkmm (bugzilla.gnome.org))
8. [Bug 589197] New: no way to have an arg callback for a
Glib::OptionEntry (glibmm (bugzilla.gnome.org))
----------------------------------------------------------------------
Message: 1
Date: Sun, 19 Jul 2009 14:02:07 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 588989] optional flag in
Glib::OptionEntry cause crash is the arg is omitted
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=588989
glibmm | general | Ver: 2.20.x
------- Comment #5 from Hubert Figuiere 2009-07-19 14:02 UTC -------
It does an then crash. It is definitely not Glibmm.
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why
you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=588989.
------------------------------
Message: 2
Date: Mon, 20 Jul 2009 09:42:31 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 558017] Build failure due to some perl
macro
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=558017
gtkmm | build | Ver: unspecified
------- Comment #10 from Murray Cumming 2009-07-20 09:42 UTC -------
Could you check if that macro is installed?
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why
you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=558017.
------------------------------
Message: 3
Date: Mon, 20 Jul 2009 09:44:15 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 573482] Gtk::Builder: autoconnecting
signals
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=573482
gtkmm | general | Ver: unspecified
Murray Cumming changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|libglademm: thoughts about |Gtk::Builder: autoconnecting
|signal autoconnecting |signals
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why
you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=573482.
------------------------------
Message: 4
Date: Mon, 20 Jul 2009 10:54:03 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 573482] Gtk::Builder: autoconnecting
signals
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=573482
gtkmm | general | Ver: unspecified
------- Comment #65 from Murray Cumming 2009-07-20 10:54 UTC -------
(In reply to comment #64)
> Created an attachment (id=137454)
--> (http://bugzilla.gnome.org/attachment.cgi?id=137454&action=view) [edit]
> Gtk::Builder::connect_signals() implementation
>
> Updated the patch for svn head.
You mean git, right? Anyway, it applies cleanly. Thanks.
However, there seem to be some unrelated changes in builder.hg for get_widget()
and get_widget_derived(). Maybe that's something you'd like to submit
separately.
> But it is a real pain maintaining these patches.
> I can't give them a sufficient testing any more,
> as there are too many dependancies on sigc++ and
> glibmm.
> I guess if you won't start taking a look, this
> will go nowhere.
> Are there any chances to start pushing a trivial
> changes, like the sigc++ and glibmm one?
Well, the glibmm changes are not trivial, right? And the sigc++ one is a ABI
break (adding a virtual destructor), so no, we can't do that until we are sure
that this will be used.
I'm starting a discussion about this now on the mailing list.
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why
you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=573482.
------------------------------
Message: 5
Date: Mon, 20 Jul 2009 11:21:42 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 574530] gtkmm-documentation: html
should not rebuild when building the tarball.
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=574530
gtkmm | documentation | Ver: unspecified
Murray Cumming changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Make xsltproc more flexible |gtkmm-documentation: html
|with --nonet |should not rebuild when
| |building the tarball.
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why
you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=574530.
------------------------------
Message: 6
Date: Mon, 20 Jul 2009 11:24:53 +0000 (UTC)
From: "gtk+ (bugzilla.gnome.org)" <[email protected]>
Subject: [gtkmm bugzilla] [Bug 574935] win32:
gtk_window_set_geometry_hints() has no effect until the window is
moved
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=574935
gtk+ | win32 | Ver: 2.14.x
Murray Cumming changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
AssignedTo|gtkmm- |[email protected]
|[email protected] |
Component|general |win32
Product|gtkmm |gtk+
QAContact|gtkmm- |[email protected]
|[email protected] |
Summary|window has to be moved to |win32:
|get it to start refreshing |gtk_window_set_geometry_hint
|automatically. |s() has no effect until the
| |window is moved
------- Comment #1 from Murray Cumming 2009-07-20 11:24 UTC -------
Sorry for the delay in replying. However, I am sure this is a GTK+ bug rather
than a gtkmm bug. Reassigning.
Hopefully you can work around this by calling set_geometry_hints() before
show()ing the window.
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why
you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=574935.
------------------------------
Message: 7
Date: Mon, 20 Jul 2009 11:30:12 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 553024] switching notebook pages while
removing them fails ungracefully
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=553024
gtkmm | general | Ver: 2.4.x
Murray Cumming changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
Status|UNCONFIRMED |NEEDINFO
------- Comment #5 from Murray Cumming 2009-07-20 11:30 UTC -------
Sakari, could you please check this?
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why
you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=553024.
------------------------------
Message: 8
Date: Tue, 21 Jul 2009 01:39:32 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 589197] New: no way to have an arg
callback for a Glib::OptionEntry
To: [email protected]
Message-ID: <[email protected]/>
Content-Type: text/plain; charset=utf-8
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=589197
glibmm | general | Ver: 2.20.x
Summary: no way to have an arg callback for a Glib::OptionEntry
Product: glibmm
Version: 2.20.x
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: general
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
GNOME version: Unspecified
GNOME milestone: Unspecified
Following bug 588989,
The optional arg flag is actually only for when we pass a callback to parse the
option (G_OPTION_ARG_CALLBACK).
In Glibmm there is no way to specify this to any of the
Glib::OptionGroup::add_entry() overrides.
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why
you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=589197.
------------------------------
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
------------------------------
_______________________________________________
Gtkmm-forge mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
End of Gtkmm-forge Digest, Vol 38, Issue 7
******************************************
_______________________________________________
gtkmm-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gtkmm-list
