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. > > > > Thanks > > -- > > Matt > > _______________________________________________ > > kopete-devel mailing list > > [email protected] > > https://mail.kde.org/mailman/listinfo/kopete-devel > > 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. > 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. -- Matt _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
