From 3940710283879bb11a2f8e4f5b14dfeccf1afd35 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Tim-Philipp=20M=C3=BCller?= Date: Wed, 21 Sep 2005 15:55:12 +0000 Subject: [PATCH] docs/pwg/appendix-porting.xml: And something about newsegment events and caps-on-buffers to the porting guide (feel f... Original commit message from CVS: * docs/pwg/appendix-porting.xml: And something about newsegment events and caps-on-buffers to the porting guide (feel free to improve). --- ChangeLog | 6 ++++++ docs/pwg/appendix-porting.xml | 20 +++++++++++++++++++- 2 files changed, 25 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index d4b64dc..1a5edb8 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2005-09-21 Tim-Philipp Müller + + * docs/pwg/appendix-porting.xml: + And something about newsegment events and caps-on-buffers to + the porting guide (feel free to improve). + 2005-09-21 Andy Wingo * check/gst/gstutils.c (test_buffer_probe_n_times): Add tests for diff --git a/docs/pwg/appendix-porting.xml b/docs/pwg/appendix-porting.xml index a6fd28c..80ec450 100644 --- a/docs/pwg/appendix-porting.xml +++ b/docs/pwg/appendix-porting.xml @@ -21,13 +21,31 @@ + Discont events have been replaced by newsegment events. In 0.9, it is + essential that you send a newsegment event downstream before you send + your first buffer (in 0.8 the scheduler would invent discont events if + you forgot them, in 0.9 this is no longer the case). + + + + + In 0.9, buffers have caps attached to them. Elements should allocate + new buffers with gst_pad_alloc_buffer (). See + for more details. + + + + Most functions returning an object or an object property have been changed to return its own reference rather than a constant reference of the one owned by the object itself. The reason for this change is primarily threadsafety. This means effectively that return values of functions such as gst_element_get_pad (), - gst_pad_get_name () and many more like these + gst_pad_get_name (), + gst_pad_get_parent (), + gst_object_get_parent (), + and many more like these have to be free'ed or unreferenced after use. Check the API references of each function to know for sure whether return values should be free'ed or not. -- 2.7.4