[Gstreamer-bugs] [Bug 125739] Changed - GstPropertyProbe interface

[bugzilla-daemon at widget.gnome.org]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=125739

Changed by ds at schleef.org.

--- shadow/125739	Wed Oct 29 06:29:26 2003
+++ shadow/125739.tmp.10177	Wed Oct 29 13:44:13 2003
@@ -90,6 +90,22 @@
 
 Will result in issues. See gstosselement.c on how to open a device
 non-blocking. Imo, we should use gst_osselement_open() instead of
 open() even for probing. I'd personally suggest to create the
 probe-list at _class_init() time, not in the probe function, since the
 element can then be in another state than NULL.
+
+------- Additional Comments From ds at schleef.org  2003-10-29 13:44 -------
+We need to stop building interfaces as plugins, then.
+
+Yes, it makes more sense as a GParamSpec.  The interface wrapper code
+should support both.
+
+probe_property() may take a long time, and should be called
+specifically when the application wants the element to probe, and in
+the given thread.  get_property_info() merely returns an
+already-probed list.  It also makes sense to only allow
+probe_property() calls when the element is in NULL.
+
+The entire point of this interface is that probing can (or is allowed
+to) take a long time.  Probing (in this sense) in a class init
+function is not reasonable.