comparison: doc/reference/libpurple/tut_signals.xml
doc/reference/libpurple/tut_signals.xml
- branch
- soc.2013.gobjectification.plugins
- changeset 37028
- ec211f9d9e81
- parent 36921
- d8dce851cb72
- child 37033
- ce8b96a22ebe
equal
deleted
inserted
replaced
| 37027:8eae75e36b85 | 37028:ec211f9d9e81 |
|---|---|
| 34 The first step of using a signal is registering it with libpurple so that | 34 The first step of using a signal is registering it with libpurple so that |
| 35 callbacks may be connected to it. This is done using | 35 callbacks may be connected to it. This is done using |
| 36 <link linkend="purple-signal-register"><function>purple_signal_register()</function></link>. | 36 <link linkend="purple-signal-register"><function>purple_signal_register()</function></link>. |
| 37 Here is a slightly modified example from | 37 Here is a slightly modified example from |
| 38 <link linkend="purple-plugins-init"><function>purple_plugins_init</function></link> | 38 <link linkend="purple-plugins-init"><function>purple_plugins_init</function></link> |
| 39 in <literal>plugin.c</literal>: | 39 in <literal>plugins.c</literal>: |
| 40 | 40 |
| 41 <programlisting> | 41 <programlisting> |
| 42 purple_signal_register(purple_plugins_get_handle(), /* Instance */ | 42 purple_signal_register(purple_plugins_get_handle(), /* Instance */ |
| 43 "plugin-load", /* Signal name */ | 43 "plugin-load", /* Signal name */ |
| 44 purple_marshal_VOID__POINTER,/* Marshal function */ | 44 purple_marshal_VOID__POINTER,/* Marshal function */ |
