pad: fix activate docs

This commit is contained in:
Wim Taymans 2012-09-28 10:41:54 +02:00
parent 58d21a49d1
commit ef012f8e58
2 changed files with 6 additions and 6 deletions

View file

@ -909,9 +909,8 @@ post_activate (GstPad * pad, GstPadMode new_mode)
* push or pull mode, just return. Otherwise dispatches to the pad's activate
* function to perform the actual activation.
*
* If not @active, checks the pad's current mode and calls
* gst_pad_activate_push() or gst_pad_activate_pull(), as appropriate, with a
* FALSE argument.
* If not @active, calls gst_pad_activate_mode() with the pad's current mode
* and a FALSE argument.
*
* Returns: #TRUE if the operation was successful.
*
@ -1449,8 +1448,8 @@ gst_pad_mark_reconfigure (GstPad * pad)
* @notify: notify called when @activate will not be used anymore.
*
* Sets the given activate function for @pad. The activate function will
* dispatch to gst_pad_activate_push() or gst_pad_activate_pull() to perform
* the actual activation. Only makes sense to set on sink pads.
* dispatch to gst_pad_activate_mode() to perform the actual activation.
* Only makes sense to set on sink pads.
*
* Call this function if your sink pad can start a pull-based task.
*/

View file

@ -309,7 +309,8 @@ typedef GstFlowReturn (*GstPadChainListFunction) (GstPad *pad, GstObject *paren
*
* This function is installed on a source pad with
* gst_pad_set_getrange_function() and can only be called on source pads after
* they are successfully activated with gst_pad_activate_pull().
* they are successfully activated with gst_pad_activate_mode() with the
* #GST_PAD_MODE_PULL.
*
* @offset and @length are always given in byte units. @offset must normally be a value
* between 0 and the length in bytes of the data available on @pad. The