view doc/core-signals.dox @ 28625:ca0d55a8943f

Dimmuxx noticed that retrieving OIM didn't work for him until he signs off and back on, and that the faltcode is such: <soap:Fault> <faultcode>AuthenticationFailed</faultcode> <faultstring>Authentication Failed</faultstring> <detail> <TweenerChallenge xmlns="http://www.hotmail.msn.com/ws/2004/09/oim/rsi">Passport1.4 blah blah blah blah</TweenerChallenge> </detail> </soap:Fault> and so he says, "I'm pretty sure just switching badcontexttoken or adding another else if will fix it :P" As usual, ZERO amount of verification was done. But don't we have a lot of users who offered to help except they can't code? Hint hint hint.
author Ka-Hing Cheung <khc@hxbc.us>
date Tue, 15 Sep 2009 01:04:11 +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