docs: flesh out typefindelement docs some more

Mention that have-type signal may be emitted from streaming
thread or application thread, and fix a typo.
This commit is contained in:
Tim-Philipp Müller 2011-01-25 18:48:40 +00:00
parent eed2a350cb
commit af0642b6e8

View file

@ -26,7 +26,9 @@
* to the found media type. * to the found media type.
* *
* Whenever a type is found the #GstTypeFindElement::have-type signal is * Whenever a type is found the #GstTypeFindElement::have-type signal is
* emitted. * emitted, either from the streaming thread or the application thread
* (the latter may happen when typefinding is done pull-based from the
* state change function).
* *
* Plugins can register custom typefinders by using #GstTypeFindFactory. * Plugins can register custom typefinders by using #GstTypeFindFactory.
*/ */
@ -53,8 +55,8 @@
* is assumed that the peer element is happy with whatever format we * is assumed that the peer element is happy with whatever format we
* eventually read. * eventually read.
* *
* By default it tries to do pull based typefinding (this avoid joining received * By default it tries to do pull based typefinding (this avoids joining
* buffers and holding them back in store.) * received buffers and holding them back in store.)
* *
* When the element has no connected srcpad, and the sinkpad can operate in * When the element has no connected srcpad, and the sinkpad can operate in
* getrange based mode, the element starts its own task to figure out the * getrange based mode, the element starts its own task to figure out the