[gstreamer-bugs] [Bug 435880] New: [GstBin] Property to allow bins to handle child async changes

[GStreamer (bugzilla.gnome.org)]

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=435880

  GStreamer | gstreamer (core) | Ver: HEAD CVS
           Summary: [GstBin] Property to allow bins to handle child async
                    changes
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: bilboed at bilboed.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


When modifying the state of childs of a bin in a different way than standard,
that bin becomes responsible for handling the state changes of element that
change state asynchronously.

With the current async-start/async-done additions, this doesn't happen anymore
if the bin is not a toplevel one (GstPipeline).

There should be a property on GstBin to specify that the given bin needs to
respond to async-start/async-done itself, not post them upstream, and start
state-continuation threads in order to move the async-changing elements to the
proper state.


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