Lines Matching full:signals
845 to register the interface's signals if there are any (we will see a bit
863 /* add properties and signals to the interface here */
1223 <chapter id="howto-signals">
1224 <title>How to create and use signals</title>
1238 possible to use GSignal for much more than just emit signals which
1242 <sect1 id="howto-simple-signals">
1243 <title>Simple use of signals</title>
1246 The most basic use of signals is to implement simple event
1307 marshallers for your signals you should probably use glib-genmarshal
1315 with a better example than writing a buffer using synchronous signals.
1414 which emits signals, I would thus urge you to create all your signals with the G_SIGNAL_RUN_LAST such that your users
1584 <title>How users can abuse signals (and why some think it is good)</title>
1586 <para>Now that you know how to create signals to which the users can connect easily and at any point in
1642 many GTK+ and GNOME applications) using signals uses a small
1660 /* signals */
1698 you must remember the whole reason for the use of these signals. The goal here is to delegate
1700 one of the class functions. The alternative to subclassing, that is, the use of signals
