gst/gsterror.c: Documents how to receive errors.

Original commit message from CVS:
* gst/gsterror.c:
Documents how to receive errors.
This commit is contained in:
Stefan Kost 2006-09-15 21:30:00 +00:00
parent 9676117fff
commit d42dbfb91a
2 changed files with 10 additions and 1 deletions

View file

@ -1,3 +1,8 @@
2006-09-16 Stefan Kost <ensonic@users.sf.net>
* gst/gsterror.c:
Documents how to receive errors.
2006-09-15 Wim Taymans <wim@fluendo.com> 2006-09-15 Wim Taymans <wim@fluendo.com>
* tools/gst-launch.c: (sigint_handler_sighandler), (check_intr), * tools/gst-launch.c: (sigint_handler_sighandler), (check_intr),

View file

@ -44,7 +44,9 @@
* processing. In short, an element doesn't know what it is being used for. * processing. In short, an element doesn't know what it is being used for.
* *
* It is the application or compound element using the given element that * It is the application or compound element using the given element that
* has more context about the use of the element. The thrown errors should * has more context about the use of the element. Errors can be received by
* listening to the #GstBus of the element/pipeline for #GstMessage objects with
* the type %GST_MESSAGE_ERROR or %GST_MESSAGE_WARNING. The thrown errors should
* be inspected, and filtered if appropriate. * be inspected, and filtered if appropriate.
* *
* An application is expected to, by default, present the user with a * An application is expected to, by default, present the user with a
@ -92,6 +94,8 @@
* passed. #GST_ERROR_SYSTEM can be used as a shortcut to give * passed. #GST_ERROR_SYSTEM can be used as a shortcut to give
* debug information on a system call error.</para></listitem> * debug information on a system call error.</para></listitem>
* </itemizedlist> * </itemizedlist>
*
* Last reviewed on 2006-09-15 (0.10.10)
*/ */
#ifdef HAVE_CONFIG_H #ifdef HAVE_CONFIG_H