FaSTTUBe/GST-Tensordecoder-ov_ep
61
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

gio: Add documentation for the new "not-mounted" and "file-exists" messages

Browse Source
This commit is contained in:
Sebastian Dröge 2009-07-10 11:24:05 +02:00
parent b9c79380aa
commit d5154874cb
2 changed files with 24 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
ext/gio/gstgiosink.c
View File

@ -27,6 +27,18 @@
* by an URI. This location can be specified using any protocol supported by * by an URI. This location can be specified using any protocol supported by
* the GIO library or it's VFS backends. Common protocols are 'file', 'ftp', * the GIO library or it's VFS backends. Common protocols are 'file', 'ftp',
* or 'smb'. * or 'smb'.
*
* If the URI or #GFile already exists giosink will post a message of
* type %GST_MESSAGE_ELEMENT with name "file-exists" on the bus. The message
* also contains the #GFile and the corresponding URI.
* Applications can use the "file-exists" message to notify the user about
* the problem and to set a different target location or to remove the
* existing file. Note that right after the "file-exists" message a normal
* error message is posted on the bus which should be ignored if "file-exists"
* is handled by the application, for example by calling
* gst_bus_set_flushing(bus, TRUE) after the "file-exists" message was
* received and gst_bus_set_flushing(bus, FALSE) after the problem is
* resolved.
* *
* <refsect2> * <refsect2>
* <title>Example pipelines</title> * <title>Example pipelines</title>

12
ext/gio/gstgiosrc.c
View File

@ -28,6 +28,18 @@
* the GIO library or it's VFS backends. Common protocols are 'file', 'http', * the GIO library or it's VFS backends. Common protocols are 'file', 'http',
* 'ftp', or 'smb'. * 'ftp', or 'smb'.
* *
* If an URI or #GFile is not mounted giosrc will post a message of type
* %GST_MESSAGE_ELEMENT with name "not-mounted" on the bus. The message
* also contains the #GFile and the corresponding URI.
* Applications can use the "not-mounted" message to mount the #GFile
* by calling g_file_mount_enclosing_volume() and then restart the
* pipeline after the mounting has succeeded. Note that right after the
* "not-mounted" message a normal error message is posted on the bus which
* should be ignored if "not-mounted" is handled by the application, for
* example by calling gst_bus_set_flushing(bus, TRUE) after the "not-mounted"
* message was received and gst_bus_set_flushing(bus, FALSE) after the
* mounting was successful.
*
* <refsect2> * <refsect2>
* <title>Example launch lines</title> * <title>Example launch lines</title>
* |[ * |[