* removed. If you wish to use the @clip after this function, make sure you
* call gst_object_ref() before removing it from the @layer.
*
- * Returns: TRUE if the clip could be removed, FALSE if the layer does
+ * Returns: %TRUE if the clip could be removed, %FALSE if the layer does
* not want to remove the clip.
*/
gboolean
*
* The reference to the @timeline will be stolen by the @pipeline.
*
- * Returns: TRUE if the @timeline could be successfully set on the @pipeline,
- * else FALSE.
+ * Returns: %TRUE if the @timeline could be successfully set on the @pipeline,
+ * else %FALSE.
*/
gboolean
ges_pipeline_set_timeline (GESPipeline * pipeline, GESTimeline * timeline)
*
* Creates a timeline from the given URI.
*
- * Returns (transfer floating) (nullable): A new timeline if the uri was loaded
- * successfully, or NULL if the uri could not be loaded.
+ * Returns: (transfer floating) (nullable): A new timeline if the uri was loaded
+ * successfully, or %NULL if the uri could not be loaded.
*/
GESTimeline *
ges_timeline_new_from_uri (const gchar * uri, GError ** error)
* directly executed in the non-linear engine. Call this method once you are
* done with a set of changes and want it to be executed.
*
- * The GESTimeline::commited signal will be emitted when the (possibly updated)
+ * The #GESTimeline::commited signal will be emitted when the (possibly updated)
* #GstPipeline is ready to output data again, except if the state of the
* timeline was #GST_STATE_READY or #GST_STATE_NULL.
*
*
* You should not try to change the state of the timeline, seek it or add
* tracks to it during a commit operation, that is between a call to this
- * function and after receiving the GESTimeline::commited signal.
+ * function and after receiving the #GESTimeline::commited signal.
*
* See #ges_timeline_commit_sync if you don't want to bother with waiting
* for the signal.