From 4e06fccf417839589c2df75112d0fcedd7823edf Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Tue, 5 Jun 2012 14:38:25 +0200 Subject: [PATCH] docs: talk about the filter caps --- docs/design/part-negotiation.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/design/part-negotiation.txt b/docs/design/part-negotiation.txt index f01b9b1..c48b1ec 100644 --- a/docs/design/part-negotiation.txt +++ b/docs/design/part-negotiation.txt @@ -32,7 +32,9 @@ A pad can ask the peer pad for its supported GstCaps. It does this with the CAPS query. The list of supported caps can be used to choose an appropriate GstCaps for the data transfer. The CAPS query works recursively, elements should take their peers into -consideration when constructing the possible caps. +consideration when constructing the possible caps. Because the result caps +can be very large, the filter can be used to restrict the caps. Only the +caps that match the filter will be returned as the result caps. (in) "filter", GST_TYPE_CAPS (default NULL) - a GstCaps to filter the results against -- 2.7.4