Re: Visor Edge and KPilot

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 23 May 2002 20:24, Peter L. Berghold wrote:
> I have noticed a few issues in that the Kalendar -> DateBook conduit does
> wacky things. Every time I sync it duplicates certain recurring events such
> that on any given day that the event lands on I end up with a copy of it
> for every time I sync.

Which Version of KPIlot are you using exactly, or rather, which KDE Version 
are you using? If you are using KPilot that came with KDE 3.0.1, there are 
several known bugs, one of which you describe. The duplicates happen when the 
user does not do a backup sync with KPIlot before the first ordinary hot 
sync. Unfortunately until three or four days ago, the code to fetch the 
database from the palm (to avoid the necessity of an explicit backup prior to 
the first sync) was not really working well and resulted in these duplicates 
you describe. 
However, there is a quick fix for your problem:
1) delete the file ~/.kde3/share/apps/kpilot/DBBackup/Palm 
Username/DatebookDB.pdb and ToDoDB.pdb in the same directory. (of course 
replace "Palm Username" with the real palm username, and the kde preferences 
directory might be ~/.kde/ on some systems (or whatever you set $KDEHOME to)
2) do a backup sync in KPIlot with all conduits turned off (this will create 
the files you just deleted again, but this time they are working!)
3) now you can do hot syncs with the calendar conduits without duplicates.

I hope this fixes your problem.

However, there is another embarrassing bug in the conduit, which might prevent 
you from seriously working with the conduit: When you do a hotsync, the 
entries on the palm stay marked as modified, so they are again copied to the 
pc on all future syncs. If you also change the entry on the PC, the changes 
on the PC will be overwritten with the Palm one when you do the next hotsync.
(Yes, I know, there should be some working conflict resolution if both the 
palm and pc entry are marked as modified, which is the third issue in the 
version that shipped with kde 3.0.1).

I fixed all these three serious problems three or four days ago, which 
unfortunately was about a week to late to make it into kde 3.0.1. The next 
kde release should finally have a working conduit with all those things 
ironed out.


> The other oddity that I have seen so far is that date entries are one day
> off from when they are supposed to be.

Hmm. Are all entries off by one day, or just those with a weekly recurrance? 
With the latter I had some problems in the past. I thought I had fixed that a 
few weeks ago, so it really depends on which version you are using (it works 
for me with the latest version from cvs). 
Adriaan, when and how are the version numbers of KPilot increased? I.e. when 
did it reach 4.2.3?



Regards,
Reinhold

PS: Peter, on your homepage www.berghold.net, most links are dead...


- -- 
- ------------------------------------------------------------------
DI Reinhold Kainhofer, Graz, Austria
email: reinhold@xxxxxxxxxxxxx, http://reinhold.kainhofer.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE87V2iTqjEwhXvPN0RAmBJAKDSX1phVfdnTukzWMY8EJuQhzMukQCg0WVK
s0juhp6mr5VSC5/sTe2IQmo=
=w95J
-----END PGP SIGNATURE-----
_______________________________________________
kde-pim mailing list
kde-pim@xxxxxxxxxxxx
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/