[gstreamer-bugs] [Bug 522205] move GST_PARAM_CONTROLLABLE out of gstcontroller.h and define further flags

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

  GStreamer | gstreamer (core) | Ver: HEAD CVS




------- Comment #6 from Stefan Kost (gstreamer, gtkdoc dev)  2008-03-14 19:03 UTC -------
If any object-property of an element is marked as CONTROLLABLE the elements
needs to do gst_object_sync_values(). Otheriwse the GstController won't work.

What I was emphasizing is the view on the element-interface from the
application. In a media player one plugs elements that are needed to decode a
clip. If there are multiple choise we use the rank. In a contents creation
application (like pitivi or buzztard) the application needs to figure e.g. what
elements can be used are a source for a timeline and what as effects and so on.
Elements with controllable properties are good candidates. Then those apps need
to generate a ui. Looking at the controllable flag provides a useful hint to
divide properties into dynamic and static ones, where one would not offer the
static ones for modification when the pipeline is playing (e.g. location of
filesrc).

CONTROLLABLE is just a flag. If its used the application can rely on the fact
that the GstController can be attached to those properties, but if an
application like cheese just wants to offer three sliders for realtime control
thats fine too.


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