view doc/log-signals.dox @ 19894:0ac0e112a0fa

Add some stuff so that we don't have to traverse over a list to determine whether a node in the buddylist has a conversation for it or not. Instead, maintain the information about conversations with the blist-node's ui-data. Looking at the ui-data can thus quickly tell us whether there's any hidden conversation with the node. We can also use this for other purposes later.
author Sadrul Habib Chowdhury <imadil@gmail.com>
date Tue, 04 Sep 2007 07:56:10 +0000
parents 8cf53d7a0887
children e0613cf8c493
line wrap: on
line source

/** @page log-signals Log Signals

 @signals
  @signal log-timestamp
 @endsignals

 <hr>

 @signaldef log-timestamp
  @signalproto
char *(*log_timestamp)(PurpleLog *log, time_t when);
  @endsignalproto
  @signaldesc
   Emitted to allow plugins to customize the timestamp on a message
   being logged.
  @param log The log the message belongs to.
  @param when The time to be converted to a string.
  @return A textual representation of the time, or @c NULL to use a
          default format.
  @note Plugins must be careful of logs with a type of PURPLE_LOG_SYSTEM.
 @endsignaldef

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