Mercurial > pidgin.yaz
annotate doc/notify-signals.dox @ 13925:60f39c405dff
[gaim-migrate @ 16442]
It is currently possible for yourself to not show up in your own
buddy list at signon with Jabber. To reproduce:
1. Sign on and add yourself to your buddy list
2. Sign off and exit Gaim
3. Delete your blist.xml
4. Sign on
The same bug would also appear when signing into your Jabber
account using Gaim for the first time.
Normally this works because the Jabber PRPL fakes showing your status
whenever jabber_presence_send() is called. However, the call to
jabber_presence_send() can happen BEFORE we receive the roster from the
server (it usually does, I think) so the PRPL tries to set the status
for yourself, but your GaimBuddy node doesn't exist yet.
committer: Tailor Script <tailor@pidgin.im>
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Thu, 06 Jul 2006 08:24:26 +0000 |
parents | 216988c717da |
children | faa6afdcea39 |
rev | line source |
---|---|
12129 | 1 /** @page conversation-signals Notification Signals |
2 | |
3 @signals | |
4 @signal displaying-userinfo | |
5 @endsignals | |
6 | |
7 @signaldef displaying-userinfo | |
8 @signalproto | |
9 void (*displaying_userinfo)(GaimAccount *account, const char *who, char **infotext); | |
10 @endsignalproto | |
11 @signaldesc | |
12 Emitted before userinfo is handed to the UI to display. | |
13 @a infotext is a pointer to a string, so a plugin can replace the text that | |
14 will be displayed. | |
15 @note | |
16 Make sure to free @a *infotext before you replace it! | |
17 @param account The account on which the info was obtained. | |
18 @param who The screen name of the user whose info is to be displayed. | |
19 @param infotext A pointer to the userinfo text to be displayed. | |
20 @endsignaldef | |
21 | |
22 */ | |
23 // vim: syntax=c tw=75 et |