I think that now that it's easy to re-enable accounts that got a connection

Sun, 30 Dec 2007 12:36:56 +0000

author
Will Thompson <resiak@pidgin.im>
date
Sun, 30 Dec 2007 12:36:56 +0000
changeset 22089
b61f17ea0f68
parent 22088
70a0fddec0a0
child 22091
1568343b965c

I think that now that it's easy to re-enable accounts that got a connection
error, this TODO is obsolete.

pidgin/gtkconn.c file | annotate | diff | comparison | revisions
--- a/pidgin/gtkconn.c	Sat Dec 29 23:27:11 2007 +0000
+++ b/pidgin/gtkconn.c	Sun Dec 30 12:36:56 2007 +0000
@@ -162,11 +162,6 @@
 		if (info != NULL)
 			g_hash_table_remove(auto_reconns, account);
 
-		/*
-		 * TODO: Do we really want to disable the account when it's
-		 * disconnected by wants_to_die?  This happens when you sign
-		 * on from somewhere else, or when you enter an invalid password.
-		 */
 		purple_account_set_enabled(account, PIDGIN_UI, FALSE);
 	}
 

mercurial