Mercurial > pidgin
view doc/log-signals.dox @ 23662:7b2fdeb078cd
take an extra reference to PurpleXfer so we can check whether the whole
thing went away. I haven't tested this because it's late, but it shouldn't
break things or at least shouldn't make things worse.
It would be great if someone can test this and let me know.
References #6246
author | Ka-Hing Cheung <khc@hxbc.us> |
---|---|
date | Thu, 07 Aug 2008 07:07:32 +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