From 2895fc6fcae3429a16daa066a765d6f57b2e2faf Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Fri, 12 Oct 2012 13:15:48 +0200 Subject: [PATCH] manual: no more new-decoded-pad --- docs/manual/basics-elements.xml | 2 +- docs/manual/basics-pads.xml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/manual/basics-elements.xml b/docs/manual/basics-elements.xml index 33b805f0e5..8f81493548 100644 --- a/docs/manual/basics-elements.xml +++ b/docs/manual/basics-elements.xml @@ -557,7 +557,7 @@ main (int argc, automatically, so it's usually only necessary to set the state of the top-level pipeline to start up the pipeline or shut it down. However, when adding elements dynamically to an already-running pipeline, e.g. - from within a "pad-added" or "new-decoded-pad" signal callback, you + from within a "pad-added" signal callback, you need to set it to the desired target state yourself using gst_element_set_state () or gst_element_sync_state_with_parent (). diff --git a/docs/manual/basics-pads.xml b/docs/manual/basics-pads.xml index 91c6a5aa17..c490a25f77 100644 --- a/docs/manual/basics-pads.xml +++ b/docs/manual/basics-pads.xml @@ -120,7 +120,7 @@ main (int argc, It is not uncommon to add elements to the pipeline only from within - the "pad-added" or "new-decoded-pad" callback. If you do this, don't + the "pad-added" callback. If you do this, don't forget to set the state of the newly-added elements to the target state of the pipeline using gst_element_set_state () or