view doc/log-signals.dox @ 25977:0e93bbb7f5ca

Woo boy this function is a little crazy. I shuffled some things around: 1. We now call aim_srv_setextrainfo() after aim_locate_setprofile() This fixes the bug where, if you set an available message, then set an away message, then change your state to available but leave the same away message up, the AIM servers would use your old available message. I'm not really sure why it happens... maybe some sort of race condition in how the server parses our requests. In any case, this fixes it, and it's what the official clients seem to do (or AIM Lite at least) 2. Combine the code for stripping HTML and truncating the available message. It was happening in two places before (one for available messages and another for ICQ away messages) 3. Put our away message in the field we've been calling an "available" message. This seems to be what the official clients do. Or AIM Lite at least. I'm not sure if there will be other side effects.

/** @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