docs: fix a typo and clarify event handling a bit more

Tell about async_done messages for some events and review the _event_new_seek
docs.
This commit is contained in:
Stefan Sauer 2012-05-21 13:17:21 +02:00
parent 554b81ed24
commit fea09dfbfc
2 changed files with 5 additions and 4 deletions

View file

@ -1646,7 +1646,8 @@ gst_element_default_send_event (GstElement * element, GstEvent * event)
* This function takes owership of the provided event so you should
* gst_event_ref() it if you want to reuse the event after this call.
*
* Returns: %TRUE if the event was handled.
* Returns: %TRUE if the event was handled. Events that execute asynchronously
* (such as flushing seeks) will emit %GST_MESSAGE_ASYNC_DONE.
*
* MT safe.
*/

View file

@ -994,13 +994,13 @@ gst_event_parse_qos_full (GstEvent * event, GstQOSType * type,
* from the newly configured start position.
*
* For negative rates, playback will start from the newly configured stop
* position (if any). If the stop position if updated, it must be different from
* -1 for negative rates.
* position (if any). If the stop position is updated, it must be different from
* -1 (#GST_CLOCK_TIME_NONE) for negative rates.
*
* It is not possible to seek relative to the current playback position, to do
* this, PAUSE the pipeline, query the current playback position with
* #GST_QUERY_POSITION and update the playback segment current position with a
* #GST_SEEK_TYPE_SET to the desired position.
* #GST_SEEK_TYPE_SET to the desired position.
*
* Returns: (transfer full): a new seek event.
*/