[gstreamer-bugs] [Bug 152864] [PATCH] GstAlsaMixer doesn't support signals

[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=152864

  GStreamer | gst-plugins-base | Ver: HEAD CVS

Jan Schmidt changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #90283|0                           |1
        is obsolete|                            |




------- Comment #44 from Jan Schmidt  2007-07-20 16:07 UTC -------
Created an attachment (id=92054)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=92054&action=view)
Updated patch

This is an updated patch. It changes:
* Deprecate the signals, but still add them to the object so that any programs
which connect to the signals don't signal a warning
* Adds some API to recognise and parse the notification messages on the bus
* Adds docs and a test for the new API
* Adds a get_flags function to retrieve flags from a mixer implementation,
similar to the GstMixerTrack/Options, allowing apps to detect whether they need
to poll for changes or not.
* Makes alsamixer check whether mute/record/volumes have changed individually
instead of sending 3 messages at once regardless of whether one of the 3 has
changed or not.

At this stage, I consider this ready to commit if people are happy with the new
API.


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