Mercurial > pidgin.yaz

view doc/notify-signals.dox @ 18608:a244c34ce59c

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Call the AIM_CB_SPECIAL_CONNERR callback from flap_connection_destroy_cb() rather than parse_flap_ch4(). This ensures that the AIM_CB_SPECIAL_CONNERR callback function gets called even if AOL ends our FLAP connection without sending the customary channel 4 FLAP. Apparently you're not allowed to be in chat rooms from two locations. So when you sign on from a second location AOL severs the chat connections from your first location. It does this by sending a TCP RST rather than the expected channel 4 FLAP. This lead to a crash if you were in a chat room, then signed on from a second location. Fixes #1937.
author Mark Doliner <mark@kingant.net>
date Sun, 22 Jul 2007 08:18:27 +0000 (2007-07-22)
parents 2177a11e169d
children cb91bb07eeff
line wrap: on
line source
/** @page notify-signals Notification Signals

 @signals
  @signal displaying-userinfo
 @endsignals

 @signaldef displaying-userinfo
  @signalproto
void (*displaying_userinfo)(PurpleAccount *account, const char *who, PurpleNotifyUserInfo *user_info);
  @endsignalproto
  @signaldesc
   Emitted before userinfo is handed to the UI to display.
   @a user_info can be manipulated via the PurpleNotifyUserInfo API in notify.c.
  @note
    If adding a PurpleNotifyUserInfoEntry, be sure not to free it -- PurpleNotifyUserInfo assumes responsibility for its objects.
  @param account   The account on which the info was obtained.
  @param who       The screen name of the user whose info is to be displayed.
  @param user_info The information to be displayed, as PurpleNotifyUserInfoEntry objects
 @endsignaldef

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