[gstreamer-bugs] [Bug 571559] Add flags to element properties to indicate valid states for changing property

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

  GStreamer | gstreamer (core) | Ver: git

Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |t.i.m at zen.co.uk




------- Comment #3 from Tim-Philipp Müller  2009-02-13 11:03 UTC -------
Not a bad idea at all, but wouldn't it make just as much sense to make all
properties that can be manipulated while the pipeline is running controllable?
That seems more user-friendly to me, since the user is likely to care only
about 'pipeline is in NULL state' and 'pipeline is running', but not about the
technical details of the states in between. (They wouldn't *have* to use the
GstController API to change the property of course).

Also, some of our state stuff is just inconsistent and unintuitive, e.g. why
wouldn't filesrc open the device in NULL->READY? It's not really READY if the
device isn't open yet, is it? But other devices are opened in NULL->READY. Do
we really want to expose all of this even more?

(Not against this at all, just thinking out loud)


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