mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-11-14 13:21:28 +00:00
79b77446d8
Original commit message from CVS: * docs/pwg/advanced-scheduling.xml: * docs/pwg/advanced-tagging.xml: * docs/pwg/advanced-types.xml: * docs/pwg/building-boiler.xml: * docs/pwg/building-chainfn.xml: * docs/pwg/building-signals.xml: * docs/pwg/building-state.xml: * docs/pwg/building-testapp.xml: * docs/pwg/intro-basics.xml: * docs/pwg/other-manager.xml: * docs/pwg/other-source.xml: Typo fixes. * docs/pwg/other-manager.xml: Add some first content. No example code yet. * gst/elements/gstfilesink.c: (gst_filesink_handle_event): Remove double newlines.
16 lines
670 B
XML
16 lines
670 B
XML
|
|
<!-- ############ chapter ############# -->
|
|
|
|
<chapter id="chapter-building-signals">
|
|
<title>Signals</title>
|
|
<para>
|
|
GObject signals can be used to notify applications of events specific
|
|
to this object. Note, however, that the application needs to be aware
|
|
of signals and their meaning, so if you're looking for a generic way
|
|
for application-element interaction, signals are probably not what
|
|
you're looking for. In many cases, however, signals can be very useful.
|
|
See the <ulink type="http"
|
|
url="http://www.le-hacker.org/papers/gobject/index.html">GObject
|
|
documentation</ulink> for all internals about signals.
|
|
</para>
|
|
</chapter>
|