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 556560] gtk_source_language_manager_guess_language
wrapper missing (gnomemm (bugzilla.gnome.org))
2. [Bug 564005] Valgrind errors and crash on exit with
Gtk::UIManager (gtkmm (bugzilla.gnome.org))
3. [Bug 564005] Valgrind errors and crash on exit with
Gtk::UIManager (gtkmm (bugzilla.gnome.org))
4. [Bug 563664] Packaging incomplete for Schema/SchemaValidator
on win32 (gtkmm (bugzilla.gnome.org))
5. [Bug 562810] Extending the extra defs generation tool to
accept custom pointer determining function
(glibmm (bugzilla.gnome.org))
6. [Bug 563664] Packaging incomplete for Schema/SchemaValidator
on win32 (gtkmm (bugzilla.gnome.org))
----------------------------------------------------------------------
Message: 1
Date: Fri, 12 Dec 2008 11:44:25 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 556560]
gtk_source_language_manager_guess_language wrapper missing
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=556560
gnomemm | gtksourceviewmm | Ver: unspecified
Murray Cumming changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Comment #2 from Murray Cumming 2008-12-12 11:44 UTC -------
Committed. Thanks. Sorry for the delay.
--
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=556560.
------------------------------
Message: 2
Date: Fri, 12 Dec 2008 14:52:43 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 564005] Valgrind errors and crash on
exit with Gtk::UIManager
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=564005
gtkmm | general | Ver: 2.14.x
Jonathon Jongsma (jonner) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
------- Comment #5 from Jonathon Jongsma (jonner) 2008-12-12 14:52 UTC -------
I really don't think that sigc::ref is the right answer. This may no longer
give you valgrind warnings because you're binding a *reference* to the smart
pointer, which doesn't take a reference on the underlying Action object. That
means that the Action object doesn't get kept alive for longer, but it also
means that you've got an invalid refptr reference as soon as the refptr that
you've passed to sigc::ref() goes out of scope, and as far as I can tell, that
will be at the end of the constructor. Be very careful about using sigc::ref
(or using references at all) with smart pointers.
--
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=564005.
------------------------------
Message: 3
Date: Fri, 12 Dec 2008 14:56:07 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 564005] Valgrind errors and crash on
exit with Gtk::UIManager
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=564005
gtkmm | general | Ver: 2.14.x
------- Comment #6 from Murray Cumming 2008-12-12 14:56 UTC -------
(In reply to comment #5)
> I really don't think that sigc::ref is the right answer.
No, I doubt that too. I was just looking for quick clues. I might look at this
in more detail later.
--
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=564005.
------------------------------
Message: 4
Date: Sat, 13 Dec 2008 13:23:08 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 563664] Packaging incomplete for
Schema/SchemaValidator on win32
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=563664
gtkmm | build | Ver: 2.14.x
Armin Burgmeier changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Comment #4 from Armin Burgmeier 2008-12-13 13:23 UTC -------
Done. You normally don't send announcement emails for libxml++ releases, do
you?
ftp://ftp.gnome.org/pub/GNOME/sources/libxml++/2.24/
ftp://ftp.gnome.org/pub/GNOME/binaries/win32/gtkmm/2.14/
--
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=563664.
------------------------------
Message: 5
Date: Mon, 15 Dec 2008 22:48:48 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 562810] Extending the extra defs
generation tool to accept custom pointer determining function
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=562810
glibmm | general | Ver: unspecified
------- Comment #5 from Jos? Alburquerque 2008-12-15 22:48 UTC -------
Okay. Plug-in generation is well underway so it can be said that it's pretty
much functioning. When generating plug-ins, however, we have two options when
dealing with the plug-in defs:
1) Generate them prior to the build process (in the jhbuild environment) so
that the defs are contained in the signal defs file (the extra defs) or:
2) Generate them as the plug-ins are generated in the build process and then
use the generated defs when the generated plug-in sources are processed by
gmmproc.
I think 2) is more advantageous because it allows the build process to deal
correctly with possible differences in how plug-ins are defined in different
versions. One such example plug-in is audioresample[1]. In jhbuild its type
is named GstSpeexResample while in version 0.10.20 its type is
GstAudioResample.
When the defs are generated in jhbuild, the type name `GstSpeexResample' is
used for the defs, but when the plug-in is generated outside of jhbuild, using
version 0.10.20 of the GStreamer libraries, then the defs are not found for the
type, GstAudioResample.
If the defs are generated during the build process, the defs will always be
found for the available plug-ins on the build system. However, this patch
would be needed so that the pointer types are always correctly identified
because defs generation would be done on the fly and not supervised so no
patching could be done to the defs then.
In the audioresample example above the signals and properties are not modified,
but the type name is different, which, as a side note, brings up any ABI issues
that things like this may cause.
[1]
http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-plugins/html/gst-plugins-base-plugins-audioresample.html
--
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=562810.
------------------------------
Message: 6
Date: Tue, 16 Dec 2008 08:11:13 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 563664] Packaging incomplete for
Schema/SchemaValidator on win32
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=563664
gtkmm | build | Ver: 2.14.x
------- Comment #5 from Arjan Franzen 2008-12-16 08:11 UTC -------
I've tested the latest gtkmm-win32-devel-2.14.3-2.exe and can confirm that the
main memoryleak is still in there.
The linking problem in VS2005 with LibXML++ is solved, thats good!
I'm guessing that the
if (impl_) {
xmlSchemaFree(impl_);
}
in schema.cc did not get integrated.
--
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=563664.
------------------------------
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
------------------------------
_______________________________________________
Gtkmm-forge mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
End of Gtkmm-forge Digest, Vol 31, Issue 9
******************************************
_______________________________________________
gtkmm-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gtkmm-list
