view doc/core-signals.dox @ 26937:74c9f4f79825

Add 'jabber' to the signals output and NULL checking so it won't crash on Windows I'm baffled, but I currently get this signal output for the jabber-receiving-message signal: (22:27:44) jabber: Recv (ssl)(307): <message from='paul.aurich@gmail.com/desktop35DEABC4' to='paul@darkrain42.org/Testing' type='chat' id='purpleabb8c602'><active xmlns='http://jabber.org/protocol/chatstates'/><nos:x value='disabled' xmlns:nos='google:nosave'/><arc:record otr='false' xmlns:arc='http://jabber.org/protocol/archive'/></message> (22:27:44) signals test: received message (type=chat, id=purpleabb8c602, from=(null) to=chat) (nil) presence and IQ are fine...
author Paul Aurich <paul@darkrain42.org>
date Fri, 22 May 2009 05:31:46 +0000
parents e0613cf8c493
children 4179ab2cfe1f
line wrap: on
line source

/** @page core-signals Core Signals

 @signals
  @signal quitting
 @endsignals

 @see core.h

 <hr>

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

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