mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-11-27 04:01:08 +00:00
Code Issues 1 Projects Releases Wiki Activity

docs: spelling and formatting fixes

Browse source
This commit is contained in:
Stefan Sauer 2011-10-21 11:15:11 +02:00
parent df6044f7eb
commit ea030c9452
3 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/random/porting-to-0.11.txt
View file

@ -258,7 +258,7 @@ The 0.11 porting guide
gst_query_parse_formats_length() -> gst_query_parse_n_formats()
gst_query_parse_formats_nth() -> gst_query_parse_nth_format()
Some query utility functionsno longer use an inout parameter for the
Some query utility functions no longer use an inout parameter for the
destination/query format:
- gst_pad_query_position()
@ -313,7 +313,7 @@ The 0.11 porting guide
gst_adapter_peek() is removed, use gst_adapter_map() and gst_adapter_unmap()
to get access to raw data from the adapter.
Arguments renamed from guint to gsize.
Arguments changed from guint to gsize.
* GstBitReader, GstByteReader, GstByteWriter
gst_*_reader_new_from_buffer(), gst_*_reader_init_from_buffer() removed, get
@ -352,3 +352,4 @@ The 0.11 porting guide
uses a GValue based API now that is similar to the 0.10 API but
allows bindings to properly use GstIterator and prevents complex
return value ownership issues.

2
docs/random/status-0.11-14-jun-2011.txt
View file

@ -96,7 +96,7 @@ GstCaps optimizations
It doesn't look like we'll be able to implement GstCaps iterators to 0.11 so
Sebastian was looking for other ways to improve caps performance. One of the
lowhanging fruits was to pass the complete GstCaps structure to the
low hanging fruits was to pass the complete GstCaps structure to the
GstBaseTransform transform_caps method. This allows for better and smarter
implementations of the function at the cost of marginally more complex code.

2
gst/gstquery.c
View file

@ -1947,7 +1947,7 @@ gst_query_new_scheduling (void)
* @random_access: if random access is possible
* @sequential: if sequential access is recommended
* @minsize: the suggested minimum size of pull requests
* @maxsize: the suggested maximum size of pull requests:
* @maxsize: the suggested maximum size of pull requests
* @align: the suggested alignment of pull requests
*
* Set the scheduling properties.