docs: Fix line numbers in tutorials 1 and 2

It seems that the lines for the C code for tutorials 1 and 2 are all
off.

The remaining tutorials seem uneffected.

Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/5387>
This commit is contained in:
Leif Andersen 2023-09-24 23:21:56 -04:00 committed by GStreamer Marge Bot
parent 049859c2cb
commit d1aaf8ba0d
2 changed files with 22 additions and 22 deletions

View file

@ -76,7 +76,7 @@ We will skip GStreamer initialization, since it is the same as the
previous tutorial:
{{ C+JS_FALLBACK.md }}
{{ tutorials/basic-tutorial-2.c[13:16] }}
{{ tutorials/basic-tutorial-2.c[17:20] }}
{{ END_LANG.md }}
{{ PY.md }}
@ -118,7 +118,7 @@ platform-independent.
### Pipeline creation
{{ C+JS_FALLBACK.md }}
{{ tutorials/basic-tutorial-2.c[17:19] }}
{{ tutorials/basic-tutorial-2.c[21:23] }}
{{ END_LANG.md }}
{{ PY.md }}
@ -130,7 +130,7 @@ before they can be used, because it takes care of some clocking and
messaging functions. We create the pipeline with [gst_pipeline_new]\().
{{ C+JS_FALLBACK.md }}
{{ tutorials/basic-tutorial-2.c[25:32] }}
{{ tutorials/basic-tutorial-2.c[29:36] }}
{{ END_LANG.md }}
{{ PY.md }}
@ -205,7 +205,7 @@ properties) or inquired to find out about the element's internal state
Coming back to what's in the example above,
{{ C+JS_FALLBACK.md }}
{{ tutorials/basic-tutorial-2.c[33:35] }}
{{ tutorials/basic-tutorial-2.c[37:39] }}
{{ END_LANG.md }}
{{ PY.md }}
@ -229,7 +229,7 @@ of the tutorial is very similar to the previous one, but we are going to
add more error checking:
{{ C+JS_FALLBACK.md }}
{{ tutorials/basic-tutorial-2.c[36:43] }}
{{ tutorials/basic-tutorial-2.c[40:47] }}
{{ END_LANG.md }}
{{ PY.md }}
@ -242,7 +242,7 @@ details are given in [Basic tutorial 3: Dynamic
pipelines].
{{ C+JS_FALLBACK.md }}
{{ tutorials/basic-tutorial-2.c[44:75] }}
{{ tutorials/basic-tutorial-2.c[48:79] }}
{{ END_LANG.md }}
{{ PY.md }}

View file

@ -75,7 +75,7 @@ See how [Basic tutorial 12: Streaming] solves this issue.
Let's review these lines of code and see what they do:
{{ C+JS_FALLBACK.md }}
{{ tutorials/basic-tutorial-1.c[9:11] }}
{{ tutorials/basic-tutorial-1.c[13:15] }}
{{ END_LANG.md }}
{{ PY.md }}
@ -98,7 +98,7 @@ benefit from the GStreamer standard command-line options (more on this
in [Basic tutorial 10: GStreamer tools])
{{ C+JS_FALLBACK.md }}
{{ tutorials/basic-tutorial-1.c[13:17] }}
{{ tutorials/basic-tutorial-1.c[16:21] }}
{{ END_LANG.md }}
{{ PY.md }}
@ -155,7 +155,7 @@ only thing we are doing in this example is exiting on error, so do not
expect much feedback.
{{ C+JS_FALLBACK.md }}
{{ tutorials/basic-tutorial-1.c[18:20] }}
{{ tutorials/basic-tutorial-1.c[22:24] }}
{{ END_LANG.md }}
{{ PY.md }}
@ -172,7 +172,7 @@ In this line, [gst_element_set_state]\() is setting `pipeline` (our only
element, remember) to the `PLAYING` state, thus initiating playback.
{{ C+JS_FALLBACK.md }}
{{ tutorials/basic-tutorial-1.c[21:26] }}
{{ tutorials/basic-tutorial-1.c[25:30] }}
{{ END_LANG.md }}
{{ PY.md }}
@ -198,7 +198,7 @@ Before terminating the application, though, there is a couple of things
we need to do to tidy up correctly after ourselves.
{{ C+JS_FALLBACK.md }}
{{ tutorials/basic-tutorial-1.c[27:33] }}
{{ tutorials/basic-tutorial-1.c[37:43] }}
Always read the documentation of the functions you use, to know if you
should free the objects they return after using them.