[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Null conduit (Was: [Kde-pim] Usability help needed for KPilot)
From:       Reinhold Kainhofer <reinhold () kainhofer ! com>
Date:       2003-04-16 23:16:44
[Download RAW message or body]

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

On Wednesday 16 April 2003 23:10, Adriaan de Groot wrote:
> at least), I ended up with the dialog layout shown at
> http://www.cs.kun.nl/~adridg/snapshot10.png (17k). 

Looking at the screenshot and the explanation of the null conduit, I can't 
help but think that the NULL conduit doesn't make any sense any more. Some 
time ago, kpilot went through all databases, and the first conduit that 
wanted that database was used. If no conduit claimed a database, it was just 
backed up. If the NULL conduit claimed a database, this prevented it from 
being backed up.

Now, kpilot calls each conduit, and the conduit opens whatever database(s) it 
wants (this allows more than one conduit to sync one and the same conduit). 
And the backup backs up all databases, so the NULL conduits practically does 
not do anything and does not have any effect any more. Or do I misunderstand 
anything here?

Reinholld
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+neRcTqjEwhXvPN0RApeaAJ9QnfEcET7XIju5S5zPOkq4dD3RoACfSIbp
NsrM3AOevCZqJRVgshil8zo=
=v+LN
-----END PGP SIGNATURE-----
_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/

[prev in list] [next in list] [prev in thread] [next in thread]