Thanks for this... I'll try to take a look at this, but I feel like I should do my planned refactoring of the KWallet code in KHTML first, as it should make fixing the remaining things easier, too. On 7/22/10, Filip Brcic wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thursday, 22. July 2010. 20.59.32 Martin Sandsmark wrote: >> On Thursday 22 July 2010 20:44:30 Filip Brcic wrote: >> > I tried to add support for multiple accounts and it seams I succeeded. >> >> Nice! But is it backwards compatible (as in; it won't forget all my >> existing logins)? > > If there is no new-way info in kwallet about the particular site, then the > system drops to old-way. Therefore, when you first login to your existing > site, > existing values will be loaded and the system will offer you to save the > password. Then that password will be saved in the new way. > > So, yes, it is backwards compatible. > > - -- > Filip Brcic > WWWeb: http://www.brcha.iz.rs > Jabber : brcha@kdetalk.net > GPG 0x2537C379 > Fingerprint: 287D 5F24 50AA A36C 977F AC9A F1FD C7EB 2537 C379 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.14 (GNU/Linux) > > iQIcBAEBAgAGBQJMSJnpAAoJEPH9x+slN8N5n24P/jSTeBqiGmM0YKMsFAEzeBrl > cfL6wFmg9nS4ojuDRAmRlt9EKcqRzs9gCqpVaQG1evO1LJ7qnOUYIEvUtX5jwyT2 > QMPOW/Wm5Oa4iIs5vClFckTWgcWPmwBBe6C9s0tnVFl2A+6MmwZ9/n6f0qQ4eC66 > a//olVKjhPiuG0Laf2/pWHTVJaHh+rx6s9QGwhqpLYA87+nKYVATlPsuucwG5OLV > nNeKBCVkUfOZDOKvkzFaILN900Z1sT8BQE/PXsfdm7OWmcuEij96UR1egbx2LQQV > hYoT/cqzUGS7aH679TNFV2F5BR79ImwO/qb8URxFn2fgVjCjTw7jSgCeJTjYPFfH > TqsAfntuWF3Z/J04I8s/2E+30PWPFp556BTlGisE0KrXkaVitetf9mWaRZ48guVY > c61qQr7eF3Po0w3lq5gJEeTr01/qOrOF0B42ZRsjQFfnOsKGJwCoNKVXuJ3zYvM1 > JtAB6ww8CDghwTbVb7FyOjUm7o4gnv9qyRD3M5jNskg1SAlCiPlSkqluIVIbFDh3 > 5MhdEpktsy/uSrIRYumJZu1+AKuCrw/yqwLt0kD4MYYdCayntRPcBWOEV7EV+RUB > mUvoRwwFnzX1CNpgRJadLRkRmGRWWRU+KY22smdsSwam2LraVpAZ1WF8iqfV6g2z > cSdIgpu/nFzW9qMLScuw > =7kGP > -----END PGP SIGNATURE----- >