view doc/savedstatus-signals.dox @ 17135:acde78931954

slpcall now explicitlt references its xfer and unreferences it when it is destroyed. While it *looks* like this should *probably* have happened anyways due to the interactins between xfer_init, xfer_end, and xfer_cancel_remote, having the xfer's owner make this explicit makes the process less fragile and more obvious, and it may fix a crash as the slp is destroyed. Fixes #1070

/** @page savedstatus-signals Saved Status Signals

 @signals
  @signal savedstatus-changed
 @endsignals

 <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 tw=75 et