Mercurial > pidgin
view doc/notify-signals.dox @ 15255:2e3ffe29f9ae
[gaim-migrate @ 18045]
We occasionally get to gaim_parse_oncoming() with a user_info indicating a NULL away message for a contact who (1) is away and is still away and (2) does actually have a message. gaim_got_infoblock() will then be called shortly thereafter.
Check to ensure that the call to gaim_prpl_got_user_status() has some benefit other than potentially removing an appropriate away message; do the call if the status actually changes as a result.
This fixes an issue in which away messages would periodically flicker invisible and then visible again in the contact list for certain contacts.
committer: Tailor Script <tailor@pidgin.im>
author | Evan Schoenberg <evan.s@dreskin.net> |
---|---|
date | Fri, 22 Dec 2006 08:29:28 +0000 |
parents | 216988c717da |
children | faa6afdcea39 |
line wrap: on
line source
/** @page conversation-signals Notification Signals @signals @signal displaying-userinfo @endsignals @signaldef displaying-userinfo @signalproto void (*displaying_userinfo)(GaimAccount *account, const char *who, char **infotext); @endsignalproto @signaldesc Emitted before userinfo is handed to the UI to display. @a infotext is a pointer to a string, so a plugin can replace the text that will be displayed. @note Make sure to free @a *infotext before you replace it! @param account The account on which the info was obtained. @param who The screen name of the user whose info is to be displayed. @param infotext A pointer to the userinfo text to be displayed. @endsignaldef */ // vim: syntax=c tw=75 et