From: Stian J. <li...@jo...> - 2006-04-21 17:02:47
|
fre, 21,.04.2006 kl. 11.59 +0200, skrev Armin Bauer: > > Either way, it would be (very) nice with an option to "create" the other > > two fields from the N value on my phone... But you know this best. > > yes, i can generate the value from the N field. The problem appears if a > user changed the fileAs attribute in evo2. > > lets say someone replaced the fileAs attribute with which was "Doe, > John" before with "John". If we would generate the fileAs attribute > during the sync we would overwrite this change again with "Doe, John". > Dont know if there is a easy solution to this problem. I guess the best > approach would be just to generate these fields and hope not too many > people fill in custom values. But does todays behaviour work fine for everyone except me? If so, could you please consider have an option forcing only syncing the "N"-value, and generating the other two from that one? There are at least some P910 users out there... > > > >> this was a bug in libsyncml. i fixed it now in the dev branch of > >> libsyncml. please run: > >> > >> svn switch http://svn.opensync.org/libsyncml/branches/6620-branch . > >> > >> in the main libsyncml directory to switch to this branch. > >> > >> please let me know if this problem is fixed then. > > > > I'll test this after work :)' And it works perfect :) Only one big "bug" preventing me from using OpenSync for real now :) Thanks. -Stian |