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 551912] New: Unable to set text color of ToggleButton
using modify_text method (gtkmm (bugzilla.gnome.org))
2. [Bug 552305] New: set_property on a "caps" property fails
(gnomemm (bugzilla.gnome.org))
3. [Bug 483790] Allow for instantiating a Glib::Mutex from a
GMutex* (glibmm (bugzilla.gnome.org))
4. [Bug 552513] New: gtkmm does not build against GTK+ 2.14 on
Windows (gtkmm (bugzilla.gnome.org))
5. [Bug 552305] set_property on a "caps" property fails
(gnomemm (bugzilla.gnome.org))
6. [Bug 552513] gtkmm does not build against GTK+ 2.14 on
Windows (gtkmm (bugzilla.gnome.org))
7. [Bug 552513] gtkmm does not build against GTK+ 2.14 on
Windows (gtkmm (bugzilla.gnome.org))
----------------------------------------------------------------------
Message: 1
Date: Fri, 12 Sep 2008 05:59:38 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[EMAIL PROTECTED]>
Subject: [gtkmm bugzilla] [Bug 551912] New: Unable to set text color
of ToggleButton using modify_text method
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=551912
gtkmm | general | Ver: 2.12.x
Summary: Unable to set text color of ToggleButton using
modify_text method
Product: gtkmm
Version: 2.12.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
I am unable to modify the text color of a ToggleButton using the supplied
modify_text method. The only method that seems to do anything at all is
modify_bg. I have found a few people on the internet facing the same problem.
--
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=551912.
------------------------------
Message: 2
Date: Mon, 15 Sep 2008 02:28:01 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
<[EMAIL PROTECTED]>
Subject: [gtkmm bugzilla] [Bug 552305] New: set_property on a "caps"
property fails
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=552305
gnomemm | gstreamermm | Ver: 2.22
Summary: set_property on a "caps" property fails
Product: gnomemm
Version: 2.22
Platform: Other
OS/Version: All
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: gstreamermm
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
QAContact: [EMAIL PROTECTED]
GNOME version: 2.21/2.22
GNOME milestone: Unspecified
Please describe the problem:
If a Gst::Element has a "caps" property that expects a GstCaps argument it is
impossible to set it using the c++ interface.
Steps to reproduce:
1. create a element that expects a "caps" property line multifilesrc or
capsfilter
2. Create a Gst::Caps object.
3. use the set_element("caps", caps) to set the caps property.
Actual results:
The program does not compile with a template instantiation error:
/usr/include/glibmm-2.4/glibmm/value.h: In static member function ?static
GType Glib::Value<Glib::RefPtr<T_CppObject> >::value_type() [with T =
Gst::Caps]?:
/usr/include/glibmm-2.4/glibmm/objectbase.h:219: instantiated from ?void
Glib::ObjectBase::set_property(const Glib::ustring&, const PropertyType&) [with
PropertyType = Glib::RefPtr<Gst::Caps>]?
teste.cpp:44: instantiated from here
/usr/include/glibmm-2.4/glibmm/value.h:233: error: ?get_base_type? is not a
member of ?Gst::Caps?
/usr/include/glibmm-2.4/glibmm/value.h: In member function ?void
Glib::Value<Glib::RefPtr<T_CppObject> >::set(const Glib::RefPtr<T_CppObject>&)
[with T = Gst::Caps]?:
/usr/include/glibmm-2.4/glibmm/objectbase.h:221: instantiated from ?void
Glib::ObjectBase::set_property(const Glib::ustring&, const PropertyType&) [with
PropertyType = Glib::RefPtr<Gst::Caps>]?
teste.cpp:44: instantiated from here
/usr/include/glibmm-2.4/glibmm/value.h:235: error: no matching function for
call to ?Glib::Value<Glib::RefPtr<Gst::Caps> >::set_object(Gst::Caps*)?
/usr/include/glibmm-2.4/glibmm/value.h:129: note: candidates are: void
Glib::ValueBase_Object::set_object(Glib::ObjectBase*)
Expected results:
The program should compile.
Does this happen every time?
yes.
Other information:
If I try to set the the g_object directly using caps->gobj() the program
compiles but the operation fails at runtime stating that "GLib-GObject-WARNING
**: unable to set property `caps' of type `GstCaps' from value of type
`glibmm__CustomPointer_P8_GstCaps'"
using the C interface g_object_set(element->gobj(), "caps", caps->gobj()); does
seem to work, my test program do give me a warning(*) but the caps is correctly
applied.
*) "GLib-GObject-WARNING **: IA__g_object_set_valist: object class
`GstMultiFileSrc' has no property named [EMAIL PROTECTED]'"
--
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=552305.
------------------------------
Message: 3
Date: Tue, 16 Sep 2008 03:17:08 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
<[EMAIL PROTECTED]>
Subject: [gtkmm bugzilla] [Bug 483790] Allow for instantiating a
Glib::Mutex from a GMutex*
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=483790
glibmm | threads | Ver: 2.14.x
Milosz Derezynski changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
------- Comment #4 from Milosz Derezynski 2008-09-16 03:17 UTC -------
I had the same idea regarding ownership with a MutexWithoutOwnership class, but
this would be like you said a bad choice regarding the virtual dtor, which can
be changed in a later release of glibmm but then we could as well make the
change of a bool arg to Glib::Mutex regarding the ownership, so it all hinges
on breaking the ABI.
Adding such a class temporarily would be, needless to say, very bad, since
people would incorporate this in their code, and finally when a bool arg to
Glib::Mutex(GMutex*) is introduced, well, I'll just stop here as it can be
clearly seen that this is just BAD! :)
I'd argue for introducing the boolean parameter at the next ABI break, so far I
have no better idea.
--
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=483790.
------------------------------
Message: 4
Date: Tue, 16 Sep 2008 15:54:14 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[EMAIL PROTECTED]>
Subject: [gtkmm bugzilla] [Bug 552513] New: gtkmm does not build
against GTK+ 2.14 on Windows
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=552513
gtkmm | build | Ver: unspecified
Summary: gtkmm does not build against GTK+ 2.14 on Windows
Product: gtkmm
Version: unspecified
Platform: Other
OS/Version: Windows
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: build
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
QAContact: [EMAIL PROTECTED]
GNOME version: Unspecified
GNOME milestone: Unspecified
Two functions have changed their signature from GTK+ 2.12 to GTK+ 2.14:
gdk_drag_get_protocol_for_display now returns a GdkNativeWindow instead of a
guint32, and gdk_selection_send_notify_for_display takes a GdkNativeWindow
instead of a guint32 as second parameter. On linux, those two are probably the
same. However, on Windows, they are not.
The C++ wrappers for these therefore do not compile on Windows.
For gdk_drag_get_protocol_for_display we can probably just change the return
type, since this does not change the ABI (does it?)
For gdk_selection_send_notify_for_display we cannot simply change the parameter
since this would break the ABI. I wonder whether we can simply add an overload
for this, even if GdkNativeWindow and guint32 are the same on Linux. If not,
then we could add the overload for Windows only.
Note that this is actually a slight API change. However, since GTK+ did the
same change it's probably OK for us as long as the ABI stays compatible.
See also
http://mail.gnome.org/archives/gtkmm-list/2008-September/msg00056.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=552513.
------------------------------
Message: 5
Date: Wed, 17 Sep 2008 01:19:06 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
<[EMAIL PROTECTED]>
Subject: [gtkmm bugzilla] [Bug 552305] set_property on a "caps"
property fails
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=552305
gnomemm | gstreamermm | Ver: 2.22
Jos? Alburquerque changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
------- Comment #1 from Jos? Alburquerque 2008-09-17 01:19 UTC -------
Would you be able to test the change just commited in svn? I think it should
fix this bug.
--
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=552305.
------------------------------
Message: 6
Date: Wed, 17 Sep 2008 01:46:14 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[EMAIL PROTECTED]>
Subject: [gtkmm bugzilla] [Bug 552513] gtkmm does not build against
GTK+ 2.14 on Windows
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=552513
gtkmm | build | Ver: unspecified
Damon Register changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
------- Comment #1 from Damon Register 2008-09-17 01:46 UTC -------
I can't say much about the compatibility issue but here is a fix that worked
for me. I used the modified gtkmm to build a simple app that works.
--
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=552513.
------------------------------
Message: 7
Date: Wed, 17 Sep 2008 01:50:57 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[EMAIL PROTECTED]>
Subject: [gtkmm bugzilla] [Bug 552513] gtkmm does not build against
GTK+ 2.14 on Windows
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=552513
gtkmm | build | Ver: unspecified
------- Comment #2 from Damon Register 2008-09-17 01:50 UTC -------
Created an attachment (id=118851)
--> (http://bugzilla.gnome.org/attachment.cgi?id=118851&action=view)
gtkmm-2.13.7\gdk\gdkmm\display.h
updates to match the gtk functions
--
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=552513.
------------------------------
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
------------------------------
_______________________________________________
Gtkmm-forge mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
End of Gtkmm-forge Digest, Vol 28, Issue 4
******************************************
_______________________________________________
gtkmm-list mailing list
gtkmm-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtkmm-list
