Mercurial > pidgin
comparison ChangeLog.API @ 21364:5a7202fa43a0
I figured a signal firing on a connection error would be useful.
author | Will Thompson <will.thompson@collabora.co.uk> |
---|---|
date | Wed, 24 Oct 2007 17:33:12 +0000 |
parents | 68098b461e00 |
children | 640551a3e75a |
comparison
equal
deleted
inserted
replaced
21363:b4833db5eed0 | 21364:5a7202fa43a0 |
---|---|
24 PurpleDisconnectReason. | 24 PurpleDisconnectReason. |
25 * PurpleConnectionUiOps.report_disconnect_reason, to be | 25 * PurpleConnectionUiOps.report_disconnect_reason, to be |
26 implemented by UIs (rather than .report_disconnect) if | 26 implemented by UIs (rather than .report_disconnect) if |
27 they want to use the reported PurpleDisconnectReason | 27 they want to use the reported PurpleDisconnectReason |
28 to give a more specific error. | 28 to give a more specific error. |
29 * A connection-error signal, fired just after the UiOp is | |
30 called. | |
29 * purple_connection_reason_is_fatal(), acting as a hint | 31 * purple_connection_reason_is_fatal(), acting as a hint |
30 to whether automatic reconnection should be attempted | 32 to whether automatic reconnection should be attempted |
31 after a connection error (rather than checking | 33 after a connection error (rather than checking |
32 gc->wants_to_die). | 34 gc->wants_to_die). |
33 | 35 |