After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 780087 - application-development: request pad example code not correct
application-development: request pad example code not correct
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: documentation
unspecified
Other Linux
: Normal normal
: 1.11.90
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-03-15 11:14 UTC by tanguy.mezzano
Modified: 2017-04-03 21:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description tanguy.mezzano 2017-03-15 11:14:28 UTC
The first code example is not correct in the "Request pads" section of:

https://gstreamer.freedesktop.org/documentation/application-development/basics/pads.html

It seems to be a copy of the second code example which is at its correct place.

Kind regards,

Tanguy Mezzano
Comment 1 Tim-Philipp Müller 2017-03-15 14:34:40 UTC
Just to make sure we're talking about the same thing:

To me it looks like both example code snippets in the Request Pads section are identical, and it looks like it should be split up, so that the first example only contains the second function, and the second example only contains the first function. Right?
Comment 2 Tim-Philipp Müller 2017-03-15 14:36:54 UTC
This looks like a bug in hotdoc to me, the markdown is correct:

--------------------------------------------------------

The following piece of code shows how you can request a new output pad
from a “tee” element:

{{ snippets.c#some_function }}

The `gst_element_get_request_pad ()` method can be used to [...]
an Ogg multiplexer from any input.

{{ snippets.c#link_to_multiplexer }}

--------------------------------------------------------
Comment 3 tanguy.mezzano 2017-03-15 14:52:12 UTC
Hi Tim-Philipp,

Indeed, code must be split up and displayed as you said.

Thanks.
Comment 4 Tim-Philipp Müller 2017-04-03 21:53:26 UTC
Should be fixed now. Apparently requires some hotdoc C extension thingy to be installed.