On Wed, Apr 05, 2006 at 09:31:42AM +0200, Olivier Goffart wrote: > Le Mercredi 5 Avril 2006 05:22, Matt Rogers a écrit : > > On Tuesday 04 April 2006 20:16, Michaël Larouche wrote: > > > Le April 4, 2006 17:55, Matt Rogers a écrit : > > > > Hi, > > > > > > > > I'm working on fixing bug #121816 which has to do with the IRC > > > > memberlist setting not being saved per chat. I have an idea about how > > > > to fix this bug and i don't think it would take me very long to > > > > implement, but I have one question. > > > > > > > > Is there something that is static (i.e. assigned once on metacontact > > > > creation and never changed again) that I can use as an identifier? I > > > > don't think that the metacontact display name is suitable enough. I'd > > > > like to use the metacontact id, but i'm not sure that those get > > > > generated for every metacontact. > > metaContactId() should be used for that. > > > > > metaContactId() could be ok, but it can change in just one case, KABC > > > association. > > > > > > if metacontact doesn't have a KABC > > > it is in the form "Protocol:accoundId:contactId" > > > > if it's of that form, it can change. unless it doesn't change when the name > > source changes. > > it's unrelated to the name source. (it take the first contact) > It's not even changed if you remove that contact or move it to another > metacontact (because it's saved to contactlist.xml) > Because of that, it may happen that to metacontact have the same id (but it > shouldn't happen often) > > It change when you change the kabc integration. > > Anyway, even if it may change, i think it suits your need for that bug. >
no, it doesn't. I don't know how much more clearer I can make this. I need an id value that will not change _EVER_. it's assigned once during metacontact creation and as long as that metacontact is in the contactlist somewhere, that id should NEVER change. if it changes when the kabc assignment changes, then it doesn't work. metacontactId() is not appropriate for my usage. i suppose i'll just invent something else. > > > > else > > > it use the id from KABC. > > > > > > And you can set KABC association after the metacontact has been created. > > > > > > But thinking of it, this is plain wrong, metaContactId() should always > > > return "Protocol:accoundId:contactId" and add extra method for KABC id. > > > > no, metaContactId() should always return some id that's random and > > pregenerated and saved in the contact list so that it can be used when > > unique identifiers are required, at least IMHO. > > > > we should then add a kabcId() function which returns the kabc id or no id > > depending upon the state of the KABC association. > > In kde4 if all contact are associated to kabc, i think the kabc id will be > suitable. (that's the plan) and as i'm sure everybody is aware, i'm against forcing all contacts to have some sort of address book association. Am I the only one that doesn't use IM as an addressbook? :( -- Matt _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
