im.pidgin.cpw.resiak.disconnectreason: 27254e6244a70a4a4ff311a6947bece3b3f5c0cb

[resiak at soc.pidgin.im]

-----------------------------------------------------------------
Revision: 27254e6244a70a4a4ff311a6947bece3b3f5c0cb
Ancestor: 7d0f6877ed2d6879f6cb69989b5eb04d633c1c93
Author: resiak at soc.pidgin.im
Date: 2007-10-27T17:41:42
Branch: im.pidgin.cpw.resiak.disconnectreason

Modified files:
        ChangeLog.API

ChangeLog: 

Changelog purple_account_get_current_error() and account-error-changed.

-------------- next part --------------
============================================================
--- ChangeLog.API	552df4c2c5240971fc14adafa334acc88b697bf0
+++ ChangeLog.API	c65b7983af269e366587c4d18863c1ad2f1178a1
@@ -27,11 +27,18 @@ version 2.3.0 (??/??/????):
 		  they want to use the reported PurpleDisconnectReason
 		  to give a more specific error.
 		* A connection-error signal, fired just after the UiOp is
-		  called.
+		  called with the same information.
 		* purple_connection_reason_is_fatal(), acting as a hint
 		  to whether automatic reconnection should be attempted
 		  after a connection error (rather than checking
 		  gc->wants_to_die).
+		* purple_account_get_current_error() to get the most recent
+		  PurpleConnectionError and description (or NULL if the
+		  account is happy with life), to allow bits of the UI to know
+		  the last error without caching it themselves (as
+		  PidginBuddyList does).
+		* An account-error-changed signal, firing when
+		  purple_account_get_current_error()'s return value changes.
 
 		* purple_util_init()
 		* purple_util_uninit()