view doc/log-signals.dox @ 23582:a270bd4b5298

Just a few little cleanups. * I think we try to pair g_strdup() with g_free(). I don't know if it actually matters, but theoretically it could. * Changed this to use g_slist_prepend() when adding stuff to the queue. * Changed purple_requesticqstatusnote() to check if the linked list is empty and return TRUE as soon as the list becomes empty rather than on the next call to that function. * Don't remove and re-add the timer if it's already set. Unless there was a reason for that?
author Mark Doliner <mark@kingant.net>
date Mon, 21 Jul 2008 07:46:23 +0000
parents 0d8061bbfc1d
children
line wrap: on
line source

/** @page log-signals Log Signals

 @signals
  @signal log-timestamp
 @endsignals

 @see log.h

 <hr>

 @signaldef log-timestamp
  @signalproto
char *(*log_timestamp)(PurpleLog *log, time_t when, gboolean show_date);
  @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.
  @param show_date Whether the date should be displayed.
  @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.doxygen tw=75 et