Send Gtkmm-forge mailing list submissions to
gtkmm-forge@...
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/gtkmm-forgeor, via email, send a message with subject or body 'help' to
gtkmm-forge-request@...
You can reach the person managing the list at
gtkmm-forge-owner@...
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 586366] New: Allow dynamic module type registration
(g_type_module_register_type) (glibmm (bugzilla.gnome.org))
2. [Bug 586366] Allow dynamic module type registration
(g_type_module_register_type) (glibmm (bugzilla.gnome.org))
3. [Bug 586269] destructors of actors on the stage not called at
end of cluttermm application (gnomemm (bugzilla.gnome.org))
4. [Bug 586437] New: TreePath::empty return true if the object
is NULL (gtkmm (bugzilla.gnome.org))
5. [Bug 586438] New: Gtk::TreeView::row_activated require a
TreeViewColumn & (gtkmm (bugzilla.gnome.org))
6. [Bug 586126] Build fails with gcc 4.4 and gtk+ 2.17.2
(gtkmm (bugzilla.gnome.org))
7. [Bug 586626] New: Clipboard::wait_for_targets() returns list
pointing to free'd memory (gtkmm (bugzilla.gnome.org))
----------------------------------------------------------------------
Message: 1
Date: Fri, 19 Jun 2009 11:13:28 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
<
bugzilla-daemon@...>
Subject: [gtkmm bugzilla] [Bug 586366] New: Allow dynamic module type
registration (g_type_module_register_type)
To:
gtkmm-forge@...
Message-ID: <
bug-586366-5595@.../>
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=586366 glibmm | object | Ver: unspecified
Summary: Allow dynamic module type registration
(g_type_module_register_type)
Product: glibmm
Version: unspecified
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: Normal
Component: object
AssignedTo:
gtkmm-forge@...
ReportedBy:
murrayc@...
QAContact:
gtkmm-forge@...
GNOME version: Unspecified
GNOME milestone: Unspecified
We need to allow classes to use
g_type_module_register_type():
http://library.gnome.org/devel/gobject/unstable/GTypeModule.html#g-type-module-register-typeinstead of g_type_register_static(), currently used in
Glib::Class::register_derived_type(), called from the derived
SomeWidget_Class::init() functions.
The custom type-registration function would then be called by a plugin entry
point, such as the entry point,
void hd_plugin_module_load(HDPluginModule* plugin);
for a Hildon Desktop Widget.
Maybe we could add an optional
_DYNAMIC_REGISTRATION()
gmmproc macro that would _add_ a
SomeWidget::register_dynamic_type(GTypeModule* module)
that could be called from the entry point function,
and we could check for that previous registration in our regular
SomeWidget_Class::init() functions to avoid a second (static) type
registration.
--
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=586366.
------------------------------
Message: 2
Date: Fri, 19 Jun 2009 13:40:32 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
<
bugzilla-daemon@...>
Subject: [gtkmm bugzilla] [Bug 586366] Allow dynamic module type
registration (g_type_module_register_type)
To:
gtkmm-forge@...
Message-ID: <
20090619134032.A8B4523F522@...>
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=586366 glibmm | object | Ver: unspecified
------- Comment #1 from Murray Cumming 2009-06-19 13:33 UTC -------
Created an attachment (id=137000)
--> (
http://bugzilla.gnome.org/attachment.cgi?id=137000&action=view)
glibmm_dynamic_gype.patch
An untested patch to implement this:
2009-06-19 Murray Cumming <
murrayc@...>
Allow dynamic GType registration, using g_type_module_register_type().
* glib/glibmm/class.[h|cc]: Added a register_derived_type() overload
that
takes an extra GTypeModule* parameter, and which calls
g_type_module_register_type() instead of g_type_register_static().
* tools/m4/class_gobject.m4:
* tools/m4/class_gtkobject.m4:
* tools/m4/class_shared.m4: Added a _DYNAMIC_GTYPE_REGISTRATION macro
to
be used in the class in the hg file, to add a
*_Class::init(GTypeModule)
method, and a get_type(GTypeModule*) method that calls it.
--
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=586366.
------------------------------
Message: 3
Date: Thu, 18 Jun 2009 13:41:58 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
<
bugzilla-daemon@...>
Subject: [gtkmm bugzilla] [Bug 586269] destructors of actors on the
stage not called at end of cluttermm application
To:
gtkmm-forge@...
Message-ID: <
20090618134159.2F6D623F507@...>
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=586269 gnomemm | cluttermm | Ver: unspecified
------- Comment #1 from Bartek Kostrzewa 2009-06-18 13:41 UTC -------
Created an attachment (id=136920)
--> (
http://bugzilla.gnome.org/attachment.cgi?id=136920&action=view)
test case for desctructor behaviour of actors
--
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=586269.
------------------------------
Message: 4
Date: Fri, 19 Jun 2009 23:41:37 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<
bugzilla-daemon@...>
Subject: [gtkmm bugzilla] [Bug 586437] New: TreePath::empty return
true if the object is NULL
To:
gtkmm-forge@...
Message-ID: <
bug-586437-5595@.../>
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=586437 gtkmm | TreeView | Ver: 2.16.x
Summary: TreePath::empty return true if the object is NULL
Product: gtkmm
Version: 2.16.x
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: TreeView
AssignedTo:
gtkmm-forge@...
ReportedBy:
hfiguiere@...
QAContact:
gtkmm-forge@...
GNOME version: Unspecified
GNOME milestone: Unspecified
TreePath::empty() does return false if the gobject_ is NULL. It should return
true, because it is invalid.
I can provide a patch if you want.
--
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=586437.
------------------------------
Message: 5
Date: Fri, 19 Jun 2009 23:46:20 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<
bugzilla-daemon@...>
Subject: [gtkmm bugzilla] [Bug 586438] New:
Gtk::TreeView::row_activated require a TreeViewColumn &
To:
gtkmm-forge@...
Message-ID: <
bug-586438-5595@.../>
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=586438 gtkmm | TreeView | Ver: 2.16.x
Summary: Gtk::TreeView::row_activated require a TreeViewColumn &
Product: gtkmm
Version: 2.16.x
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: TreeView
AssignedTo:
gtkmm-forge@...
ReportedBy:
hfiguiere@...
QAContact:
gtkmm-forge@...
GNOME version: Unspecified
GNOME milestone: Unspecified
Gtk::TreeView::row_activated() require a TreeViewColumn. But
TreeView::get_path_at_pos() can return a NULL TreeViewColumn*. So we need an
overload that either just accept a TreeViewColumn* or one that does not
require the parameter.
I can provide a patch if you want.
--
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=586438.
------------------------------
Message: 6
Date: Sat, 20 Jun 2009 22:15:06 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<
bugzilla-daemon@...>
Subject: [gtkmm bugzilla] [Bug 586126] Build fails with gcc 4.4 and
gtk+ 2.17.2
To:
gtkmm-forge@...
Message-ID: <
20090620221506.90BDF23F5A5@...>
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=586126 gtkmm | general | Ver: unspecified
Vincent Untz changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Build fails with 4.4 and |Build fails with gcc 4.4 and
|gtk+ 2.17.2 |gtk+ 2.17.2
--
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=586126.
------------------------------
Message: 7
Date: Mon, 22 Jun 2009 12:03:27 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<
bugzilla-daemon@...>
Subject: [gtkmm bugzilla] [Bug 586626] New:
Clipboard::wait_for_targets() returns list pointing to free'd memory
To:
gtkmm-forge@...
Message-ID: <
bug-586626-5595@.../>
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=586626 gtkmm | general | Ver: 2.16.x
Summary: Clipboard::wait_for_targets() returns list pointing to
free'd memory
Product: gtkmm
Version: 2.16.x
Platform: Other
OS/Version: All
Status: UNCONFIRMED
Severity: critical
Priority: Normal
Component: general
AssignedTo:
gtkmm-forge@...
ReportedBy:
pcjc2@...
QAContact:
gtkmm-forge@...
GNOME version: 2.25/2.26
GNOME milestone: Unspecified
Steps to reproduce:
Noted in inkscape, under valgrind.
Stack trace:
Other information:
> It seems that the implicit creation of a Glib::StringArrayHandle upon
> return is causing the problem. The constructor which takes a container
> (our std::list of ustring targets), does not associate ownership of the
> array elements with the newly created Glib::StringArrayHandle, it just
> stores pointers.
>
> When our "listTargets" std::list goes out of scope, its elemensts are
> free'd, thus causing the corruption / problems when our caller tries to
> use its result.
--
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=586626.
------------------------------
------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org------------------------------
_______________________________________________
Gtkmm-forge mailing list
Gtkmm-forge@...
https://lists.sourceforge.net/lists/listinfo/gtkmm-forgeEnd of Gtkmm-forge Digest, Vol 37, Issue 11
*******************************************
_______________________________________________
gtkmm-list mailing list
gtkmm-list@...
http://mail.gnome.org/mailman/listinfo/gtkmm-list