GNOME.org
 

Gtkmm-forge Digest, Vol 25, Issue 9

Send Gtkmm-forge mailing list submissions to
	gtkmm-forge lists sourceforge net

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
	gtkmm-forge-request lists sourceforge net

You can reach the person managing the list at
	gtkmm-forge-owner lists sourceforge net

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 539063] New: GhostPad wrapper lacking	something
      (gnomemm (bugzilla.gnome.org))
   2. [Bug 539063] GhostPad wrapper lacking something
      (gnomemm (bugzilla.gnome.org))
   3. [Bug 539063] GhostPad wrapper lacking something
      (gnomemm (bugzilla.gnome.org))
   4. [Bug 512348] Glib::Thread::create() does not	appear to be
      thread safe (glibmm (bugzilla.gnome.org))
   5. [Bug 538882] Unable to compile gtkmm-2.8.12 on	Slackware 12.1
      (gtkmm (bugzilla.gnome.org))
   6. [Bug 538803] [PATCH] Address Glib::Tree<> TODOs
      (glibmm (bugzilla.gnome.org))
   7. [Bug 512348] Glib::Thread::create() does not	appear to be
      thread safe (glibmm (bugzilla.gnome.org))


----------------------------------------------------------------------

Message: 1
Date: Thu, 19 Jun 2008 03:00:03 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 539063] New: GhostPad wrapper lacking
	something
To: gtkmm-forge lists sourceforge net
Message-ID: <bug-539063-5595 http bugzilla gnome org/>
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=539063

  gnomemm | gstreamermm | Ver: unspecified
           Summary: GhostPad wrapper lacking something
           Product: gnomemm
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamermm
        AssignedTo: gtkmm-forge lists sourceforge net
        ReportedBy: marcus brinkmann ruhr-uni-bochum de
         QAContact: gtkmm-forge lists sourceforge net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Please describe the problem:
Creating a ghost pad from a target pad or from a direction does not work.

Steps to reproduce:
For example:

  Glib::RefPtr<Gst::Pad> sink_pad = audio_convert->get_static_pad ("sink");

(1)

  Glib::RefPtr<Gst::Element> audio_convert
    = Gst::ElementFactory::create ("audioconvert", "audioconvert");

(2)

  Glib::RefPtr<Gst::GhostPad> ghost_pad
          = Gst::GhostPad::create ("sink", Gst::PAD_SINK);



Actual results:

(1)

(lt-mediaplayer:8954): glibmm-WARNING **:
Glib::ConstructParams::ConstructParams(): object class "gtkmm__GstGhostPad" has
no property named "target"

(2)

(lt-mediaplayer:10732): glibmm-WARNING **:
Glib::ConstructParams::ConstructParams(): object class "gtkmm__GstGhostPad" has
no property named "dir"

In either case, the ghost pad is not properly functional (has no direction).


Expected results:
I would expect a ghost pad with the given target or direction to be created.

Does this happen every time?
Yes.

Other information:
>From Jos? Alburquerque:

"What you're getting above is a warning related to how the
Gst::GhostPad::create() methods have been wrapped and an interaction between
the parameter collection for the Gst::GhostPad construction in its super
class's Gst::Pad constructor and the gstreamer object internal properties.  I
wont bore you with all the details, however, suffice it to say that thanks to
your reporting I think this can be quickly fixed."


-- 
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=539063.



------------------------------

Message: 2
Date: Thu, 19 Jun 2008 03:01:34 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 539063] GhostPad wrapper lacking
	something
To: gtkmm-forge lists sourceforge net
Message-ID: <20080619030134 14EFA23F509 label gnome org>
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=539063

  gnomemm | gstreamermm | Ver: unspecified




------- Comment #1 from Marcus Brinkmann  2008-06-19 03:01 UTC -------
Created an attachment (id=113018)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=113018&action=view)
Example program to reproduce the problem.

Put this in gstreamermm/examples/media_player_gtkmm/ and compile and run to
reproduce the 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=539063.



------------------------------

Message: 3
Date: Thu, 19 Jun 2008 04:31:13 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 539063] GhostPad wrapper lacking
	something
To: gtkmm-forge lists sourceforge net
Message-ID: <20080619043113 12A0923F519 label gnome org>
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=539063

  gnomemm | gstreamermm | Ver: unspecified

Jos? Alburquerque changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jaalburqu svn gnome org




------- Comment #2 from Jos? Alburquerque  2008-06-19 04:31 UTC -------
As I said in the list thread, the warnings seem to be pertinent but I can't
confirm the error.  Here's what I said:

This one I think should be addressed by comparing C and C++ functionality.  I
would encourage you to test both C and C++ versions (ignoring the warning above
for now) and see if there is a difference in functionality.  If you find
anything, I'll be happy to  look into it, but I'd really appreciate it if, as
already described, you could file it in bugzilla if you find a bug.  Please be
sure to post both the C and the C++ examples (as brief as possible) with the
report.  Really appreciate you testing things out.


-- 
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=539063.



------------------------------

Message: 4
Date: Thu, 19 Jun 2008 05:56:55 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 512348] Glib::Thread::create() does not
	appear to be thread safe
To: gtkmm-forge lists sourceforge net
Message-ID: <20080619055655 D401323F519 label gnome org>
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=512348

  glibmm | threads | Ver: 2.14.x




------- Comment #12 from Murray Cumming  2008-06-19 05:56 UTC -------
> when c++0x comes out by using the std::function callback wrapper, and deprecate 
> the version taking a sigc::slot object.

So std::function is safer than sigc::slot? Can't we make sigc::slot as safe as
std::function?


-- 
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=512348.



------------------------------

Message: 5
Date: Thu, 19 Jun 2008 05:59:03 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 538882] Unable to compile gtkmm-2.8.12
	on	Slackware 12.1
To: gtkmm-forge lists sourceforge net
Message-ID: <20080619055903 2680123F509 label gnome org>
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=538882

  gtkmm | build | Ver: 2.8.x

Murray Cumming changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |murrayc murrayc com




------- Comment #1 from Murray Cumming  2008-06-19 05:59 UTC -------
What version of GTK+ are you using?


-- 
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=538882.



------------------------------

Message: 6
Date: Thu, 19 Jun 2008 06:19:49 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 538803] [PATCH] Address Glib::Tree<>
	TODOs
To: gtkmm-forge lists sourceforge net
Message-ID: <20080619061949 C4B0C23F4E9 label gnome org>
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=538803

  glibmm | general | Ver: 2.17.x

Murray Cumming changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |murrayc murrayc com
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED




------- Comment #2 from Murray Cumming  2008-06-19 06:19 UTC -------
Thanks.

I made some more small changes of my own.


-- 
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=538803.



------------------------------

Message: 7
Date: Thu, 19 Jun 2008 10:10:04 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 512348] Glib::Thread::create() does not
	appear to be thread safe
To: gtkmm-forge lists sourceforge net
Message-ID: <20080619101004 D65D723F59F label gnome org>
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=512348

  glibmm | threads | Ver: 2.14.x




------- Comment #13 from Chris Vine  2008-06-19 10:10 UTC -------
The sigc::slot object itself is thread safe, but sigc::trackable, with which
the slot is registered, is not.

At the sigc level, the best thing would be to add functionality to be able to
"switch off" trackability for particular slots.  I remember some time ago
looking at whether passing the address of the slot to
sigc::trackable::remove_destroy_notify_callback() might do it (I think I found
it would not, but I remember also thinking that the sigc code was rather opaque
so that might be wrong).  If it does do it, if the trackable object itself
could be identified in Glib::Thread::create(),
sigc::trackable::remove_destroy_notify_callback() could be called in
Glib::Thread::create() on slot_copy immediately after:

  sigc::slot_base *const slot_copy = new sigc::slot<void>(slot);

However I think I also concluded that information about the trackable object
had been lost at that stage, but I am afraid it is some time since I looked at
this.

In any event, if this is to be dealt with at the sigc level, a better solution
would be either (i) to be able to pass an additional argument to
sigc::mem_fun() on slot creation which could, if changed from the default,
prevent slot registration/deregistration in the first case, (ii) to have a
compile time option which includes code which protects operations on the
std::list object maintained by each sigc::trackable object with a mutex.

The latter gives rise to dependency issues.  It is the best solution however as
it would allow different slots representing methods of the same object to be
created in different threads.  (Possibly there ought to be a more general
health warning about this in the Glib::Thread documentation, as I suspect there
might be a quantity of thread-unsafe code around because of sigc::trackable.)

Chris


-- 
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=512348.



------------------------------

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

------------------------------

_______________________________________________
Gtkmm-forge mailing list
Gtkmm-forge lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge


End of Gtkmm-forge Digest, Vol 25, Issue 9
******************************************
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]