From 85c0fc3260561d3942921e1c5efe3f4917956417 Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Mon, 15 Dec 2008 15:27:06 +0000 Subject: [PATCH] docs/design/part-TODO.txt: Remove the seqnum entry that we implemented in 0.10 already. Original commit message from CVS: * docs/design/part-TODO.txt: Remove the seqnum entry that we implemented in 0.10 already. Add entry about removing the format return value for queries. --- ChangeLog | 6 ++++++ docs/design/part-TODO.txt | 11 ++--------- 2 files changed, 8 insertions(+), 9 deletions(-) diff --git a/ChangeLog b/ChangeLog index 665163da63..a22bd0dfc1 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2008-12-15 Wim Taymans + + * docs/design/part-TODO.txt: + Remove the seqnum entry that we implemented in 0.10 already. + Add entry about removing the format return value for queries. + 2008-12-15 Wim Taymans * libs/gst/base/gstbasesink.c: (gst_base_sink_class_init), diff --git a/docs/design/part-TODO.txt b/docs/design/part-TODO.txt index a8c136f835..f06717faef 100644 --- a/docs/design/part-TODO.txt +++ b/docs/design/part-TODO.txt @@ -30,15 +30,6 @@ API/ABI already got pushed and need to be pushed again. Might need GstFlowReturn from gst_pad_push_event(). -- keep track of seeks with a counter so that we can match seek events received - in the demuxer srcpads. This is needed because a normal seek on a pipeline - will send the seek event on all sinks, which results in the demuxer receiving - the seek twice. If there is no way to see that the seek is the same, it will - perform the seek twice. - It would also be nice to have this same sequence number in the segment event - that resulted from the seek so that everything seek related can be tracked - properly. - - Optimize negotiation. We currently do a get_caps() call when we link pads, which could potentially generate a huge list of caps and all their combinations, we need to avoid generating these huge lists by generating them @@ -82,6 +73,8 @@ API/ABI - Remove the XML serialisation stuff. +- Remove the result format value in queries. + IMPLEMENTATION --------------