annotate doc/gtklog-signals.dox @ 15787:b25acae693cd
Change connection.c:gaim_connection_error() to still work even if the
message parameter is NULL. There's no reason to error-out of that
function just because some yuppie didn't pass us an error message.
But we still log a critical message, so those of you at home running
with fatal_criticals will still crash.
I noticed this because Jabber isn't handling <stream:error/> correctly
right now. Anyone else notice this? The code is written to look for
"stream:error", but our xmlnode stuff just sees "error" (even though
the "stream:error" format is sent over the wire). I think it's
because of the libxml change.
To reproduce the problem, sign onto the same resource twice and note
that the error message that Gaim gives you sucks.
| author |
Mark Doliner <mark@kingant.net> |
| date |
Tue, 13 Mar 2007 07:33:08 +0000 |
| parents |
cb36bc2db7c5 |
| children |
8cf53d7a0887 |
| rev |
line source |
|
12838
|
1 /** @page gtklog-signals GtkLog Signals
|
|
|
2
|
|
|
3 @signals
|
|
|
4 @signal log-displaying
|
|
|
5 @endsignals
|
|
|
6
|
|
|
7 <hr>
|
|
|
8
|
|
|
9 @signaldef log-displaying
|
|
|
10 @signalproto
|
|
|
11 void (*log_displaying)(GaimGtkLogViewer *viewer, GaimLog *log);
|
|
|
12 @endsignalproto
|
|
|
13 @signaldesc
|
|
|
14 Emitted when a log is being displayed.
|
|
|
15 @param viewer The log viewer
|
|
|
16 @param log The log being displayed
|
|
|
17 @endsignaldef
|
|
|
18
|
|
|
19 */
|
|
|
20 // vim: syntax=c tw=75 et
|
