Mercurial > pidgin
changeset 20110:ed4c1053c3da
Add PURPLE_REASON_INVALID_USERNAME, which should go away as soon as there's
some hook for prpls to validate the account settings before connecting.
author | Will Thompson <will.thompson@collabora.co.uk> |
---|---|
date | Tue, 18 Sep 2007 21:12:28 +0000 |
parents | 94062344397c |
children | b5ccce9a88a1 |
files | libpurple/connection.h |
diffstat | 1 files changed, 7 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/libpurple/connection.h Tue Sep 18 16:39:48 2007 +0000 +++ b/libpurple/connection.h Tue Sep 18 21:12:28 2007 +0000 @@ -71,6 +71,13 @@ */ PURPLE_REASON_NAME_IN_USE, + /** The username for the account isn't valid. + * @todo This reason really shouldn't be necessary. Usernames and + * other account preferences should be validated when the + * account is created. + */ + PURPLE_REASON_INVALID_USERNAME, + /** The server did not provide a SSL certificate. */ PURPLE_REASON_CERT_NOT_PROVIDED, /** The server's SSL certificate could not be trusted. */