view doc/log-signals.dox @ 24199:aa8ddc4e12af

GtkBlist: don't set the Urgent hint whenever a connection error occurs or is updated In principle, setting Urgent is a good idea, because the user can tell that an error has occurred. However, it winds up being repeatedly re-set every time an account tries and fails to reconnect, which is incredibly annoying. I think the right solution is to keep a set of accounts we've set urgent for, removing them from the set when they successfully connect. But not setting it at all is better than the current state.
author Will Thompson <will.thompson@collabora.co.uk>
date Sun, 28 Sep 2008 17:19:38 +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