view doc/savedstatus-signals.dox @ 29246:1428d59119cd

*** Plucked rev aada73f0d8a35997280d570f47caf30907fe68df (bcc0147bab874ca52c55ad4900545e17528bf8fd): Make sure that libpurple core knows that a buddy is on the allow list just after accepting their add request. Previously, this was not a problem, and would go away at next login, but now that the core does its own client-side blocking, it appears as if newly added buddies can't talk to you. Fixes #10898.
author Daniel Atallah <daniel.atallah@gmail.com>
date Thu, 07 Jan 2010 23:44:38 +0000
parents e0613cf8c493
children
line wrap: on
line source

/** @page savedstatus-signals Saved Status Signals

 @signals
  @signal savedstatus-changed
 @endsignals

 @see savedstatus.h

 <hr>

 @signaldef savedstatus-changed
  @signalproto
void (*savedstatus_changed)(PurpleSavedStatus *new, PurpleSavedStatus *old);
  @endsignalproto
  @signaldesc
   Emitted when a new saved status is activated.
 @endsignaldef

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