Version: 0.8.0 (using KDE 3.2 BRANCH >= 20040204, Mandrake Linux Cooker i586 - Cooker) Compiler: gcc version 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk) OS: Linux (i686) release 2.6.3-7mdk If I type in the wrong username in the account setup (like I always do for my Yahoo! login), it should be easier to fix it. currently I have to go to Kopete configuration, remove the account and create a new one! I should be able to fix the login from the login dialog - when the protoco fails to login and the dialog is displayed with the "wrong password" error, I should be able to change the login as well as the password (in my case - my IM passwords are all the same so I can't be wrong here, but I constantly misspell my login). if you decide to keep the username box in that dialog read-only, then please gray it out so the fact that it cannot be edited is visible. If not in the login dialog (and I hope that even if you do allow that), then I should be able to change the login from the Kopete Configuration->Accounts->Modify.
this is a restriction of the API.
On June 9, 2004 11:39 am, Oded Arbel wrote: > If I type in the wrong username in the account setup (like I always do for > my Yahoo! login), it should be easier to fix it. currently I have to go to > Kopete configuration, remove the account and create a new one! Indeed, IMO the account ID should not be the unique ID for the account. IRC does not do this anymore.
It's not a restriction of the API at all. It's just a restriction of how almost everyone is implementing it. Like I said, in IRC you can change everything and anything in an existing account. The API says the accountId has to be unique, thats fine. But nowhere does it say that the accountId has to represent your login credentials. It can just be a number taken from a sequence. It's up to the protocol how they do their authentication procedure, if devs wanted to they could easily make this use an account property different from accountId.
and it's still a wishlist because it's a change in the existing behavior (not to mention rather low priority from my POV). It's just not as easy as it should be.
Jason: previously accountId() was being used in the GUI, so I think for historical reasons all protocols use a formatted version of the account details as accountId(). If this has been changed now, it should be noted in the API docs and be made a TODO item for one of the future Kopete versions.
AFAIK, nothing has been changed to that effect.
*** This bug has been marked as a duplicate of 68958 ***
Is this the same as that you can't have a space character in your IRC username, which is usually "Firstname Lastname"?