docs: reword stuff about custom mainloops

Fixes #574229.
This commit is contained in:
Wim Taymans 2009-03-09 16:09:38 +01:00
parent 50fdaa4f25
commit 72101e3b14

View file

@ -174,10 +174,11 @@ g_signal_connect (bus, "message::eos", G_CALLBACK (cb_message_eos), NULL);
[..] [..]
</programlisting> </programlisting>
<para> <para>
If you aren't using GLib mainloop, the message signals won't be available If you aren't using GLib mainloop, the asynchronous message signals won't
by default. You can however use a small helper exported by to provide be available by default. You can however install a custom sync handler
integration with the mainloop you're using, and enable generation of bus that wakes up the custom mainloop and that uses
signals (see <ulink type="http" <function>gst_bus_async_signal_func ()</function> to emit the signals.
(see also <ulink type="http"
url="&URLAPI;GstBus.html">documentation</ulink> for details) url="&URLAPI;GstBus.html">documentation</ulink> for details)
</para> </para>
</sect1> </sect1>