view doc/plugin-signals.dox @ 17883:9a19c46adf66

The server's ad-hoc commands are now listed in the account's action menu. Note that this requires an additional field in the _PurplePluginAction struct. There's no other way, since there was no way to supply user_data, and dynamically created functions are not supported by C. This should be fine, since that struct is only malloced in purple_plugin_action_new, which is part of the core. Applications have to either pass the struct unmodified, or restore the user_data pointer if the action is recreated when necessary (as is the case in Adium).

/** @page plugin-signals Plugin Signals

 @signals
  @signal plugin-load
  @signal plugin-unload
 @endsignals

 <hr>

 @signaldef plugin-load
  @signalproto
void (*plugin_load)(PurplePlugin *plugin);
  @endsignalproto
  @signaldesc
   Emitted when a plugin is loaded.
  @param plugin The plugin that was loaded.
 @endsignaldef

 @signaldef plugin-unload
  @signalproto
void (*plugin_unload)(PurplePlugin *plugin);
  @endsignalproto
  @signaldesc
   Emitted when a plugin is unloaded.
  @param plugin The plugin that was unloaded.
 @endsignaldef

 */
// vim: syntax=c tw=75 et