From f7a3f36f762d5f26626f01e5db253ec8ae491548 Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Tue, 20 Mar 2007 14:17:47 +0000 Subject: [PATCH] docs/design/part-block.txt: Mention the fact that the newly switched element should be set to at least PAUSED. Original commit message from CVS: * docs/design/part-block.txt: Mention the fact that the newly switched element should be set to at least PAUSED. --- ChangeLog | 6 ++++++ docs/design/part-block.txt | 4 +++- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index 4422eef276..d3dd2b7042 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2007-03-20 Wim Taymans + + * docs/design/part-block.txt: + Mention the fact that the newly switched element should be set to at + least PAUSED. + 2007-03-20 Wim Taymans * gst/gst.c: diff --git a/docs/design/part-block.txt b/docs/design/part-block.txt index a30b1c6f22..32cf3363fd 100644 --- a/docs/design/part-block.txt +++ b/docs/design/part-block.txt @@ -138,7 +138,9 @@ Use cases: 6) link element4 and element3 7) link element1 and element4 (FIXME, how about letting element4 know about the currently running segment?, see issues.) - 8) unblock element1 src + 8) make sure element4 is in the same state as the rest of the elements. The + element should at least be PAUSED. + 9) unblock element1 src The same flow can be used to replace an element in a PAUSED pipeline. Only special care has to be taken when performing step 2) which has to be done