mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2025-02-20 13:06:23 +00:00
design/caps: better explain precendence by order when fixating caps
Drops redundancy on "structure" while at it.
This commit is contained in:
parent
0c6d5e76a8
commit
2b0e5e83ff
1 changed files with 3 additions and 3 deletions
|
@ -24,9 +24,9 @@ Caps are fixed if they only contain a single structure and this
|
|||
structure is fixed. A structure is fixed if none of its fields
|
||||
is of an unfixed type, for example a range, list or array.
|
||||
|
||||
For fixating caps only the first structure is kept as the order of
|
||||
structures is meant to express the preferences for the different
|
||||
structures. Afterwards, each unfixed field of this structure is set to
|
||||
For fixating caps only the first structure is kept, as the order in
|
||||
which they appear is meant to express their precedence.
|
||||
Afterwards, each unfixed field of this structure is set to
|
||||
the value that makes most sense for the media format by the element or
|
||||
pad implementation and then every remaining unfixed field is set to an
|
||||
arbitrary value that is a subset of the unfixed field’s values.
|
||||
|
|
Loading…
Reference in a new issue