view doc/core-signals.dox @ 31000:8a03508dd6f4

Change the "Manual" browser command pref's name to allow for a relatively simple migration of an existing value from the path pref to the new string pref. As I note in the comment in the migration code, I realize this will break things for and confuse those users who use the same config directory for mutliple versions of Pidgin, but I'm not inclined to devise a solution that will make that work. The solution I've implemented fixes the most important case--users who upgrade. The rest of the world will just have to move on. Refs #12024.
author John Bailey <rekkanoryo@rekkanoryo.org>
date Mon, 20 Sep 2010 03:53:47 +0000
parents 4179ab2cfe1f
children
line wrap: on
line source

/** @page core-signals Core Signals

 @signals
  @signal quitting
  @signal uri-handler
 @endsignals

 @see core.h

 <hr>

 @signaldef quitting
  @signalproto
void (*quitting)();
  @endsignalproto
  @signaldesc
   Emitted when libpurple is quitting.
 @endsignaldef

 @signaldef uri-handler
  @signalproto
gboolean (*uri_handler)(const gchar *proto, const gchar *cmd, GHashTable *params);
  @endsignalproto
  @signaldesc
   Emitted when handling a registered URI.
  @param proto The protocol of the URI.
  @param cmd The 'command' of the URI.
  @param params Any key/value parameters from the URI.
 @endsignaldef

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