mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-06-27 10:20:42 +00:00
Code Issues 1 Projects Releases Wiki Activity

Add blurb about how the bus goes into flushing mode and drops all messages when its bin goes from READY into NULL state.

Browse source 
Original commit message from CVS:
* docs/design/part-gstbin.txt:
* docs/design/part-gstbus.txt:
* gst/gstbus.c:
Add blurb about how the bus goes into flushing mode and
drops all messages when its bin goes from READY into NULL
state.
This commit is contained in:
Tim-Philipp Müller 2005-09-23 18:02:18 +00:00
parent 3694e3b45c
commit 2c202f9120
4 changed files with 25 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
ChangeLog
View file

@ -1,3 +1,12 @@
2005-09-23 Tim-Philipp Müller <tim at centricular dot net>
* docs/design/part-gstbin.txt:
* docs/design/part-gstbus.txt:
* gst/gstbus.c:
Add blurb about how the bus goes into flushing mode and
drops all messages when its bin goes from READY into NULL
state.
2005-09-23 Thomas Vander Stichele <thomas at apestaart dot org>
* docs/gst/gstreamer-sections.txt:

7
docs/design/part-gstbin.txt
View file

@ -55,6 +55,13 @@ external message bus, except for EOS which is handled specially.
The application can retrieve the external GstBus and integrate it in the
mainloop or it can just _pop() messages off in its own thread.
When a bin goes from READY into NULL state, it will set its bus to flushing,
ie. the bus will drop all existing and new messages on the bus. This is
necessary because bus messages hold references to the bin or its elements,
so there are circular references that need to be broken if one ever wants
to be able to destroy the bin properly.
EOS
---

6
docs/design/part-gstbus.txt
View file

@ -27,3 +27,9 @@ possible to react to a message in the same thread that posted the
message on the bus. This should only be used if the application is able
to deal with messages from different threads.
When a pipeline or bin goes from READY into NULL state, it will set its bus
to flushing, ie. the bus will drop all existing and new messages on the bus,
This is necessary because bus messages hold references to the bin/pipeline
or its elements, so there are circular references that need to be broken if
one ever wants to be able to destroy a bin or pipeline properly.

3
gst/gstbus.c
View file

@ -53,6 +53,9 @@
* to deal with messages from different threads.
*
* Every #GstBin has one bus.
*
* Note that a #GstBin will set its bus into flushing state when changing from
* READY to NULL state.
*/
#include <errno.h>