| author | zautrix <zautrix> | 2005-07-09 12:00:17 (UTC) |
|---|---|---|
| committer | zautrix <zautrix> | 2005-07-09 12:00:17 (UTC) |
| commit | fa0b6f9dae69ae7ac610b2bc97ca79b74d04f5e5 (patch) (side-by-side diff) | |
| tree | b8d4b3cec0f447fb2930fe2ab9cd191bf7e015d0 /bin/kdepim | |
| parent | 2e2d9a949b8273ad52b09ffdf2c9250acfdbe6db (diff) | |
| download | kdepimpi-fa0b6f9dae69ae7ac610b2bc97ca79b74d04f5e5.zip kdepimpi-fa0b6f9dae69ae7ac610b2bc97ca79b74d04f5e5.tar.gz kdepimpi-fa0b6f9dae69ae7ac610b2bc97ca79b74d04f5e5.tar.bz2 | |
fixx
| -rw-r--r-- | bin/kdepim/WhatsNew.txt | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt index 8fab725..2ce78c7 100644 --- a/bin/kdepim/WhatsNew.txt +++ b/bin/kdepim/WhatsNew.txt @@ -17,2 +17,3 @@ Now pi-sync behaviour should be: 3) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ). + If the data which local receives contains entries which are on disabled calendars on local this entries are updated and not added as duplicates to the default calendar. 4) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote. @@ -20,3 +21,6 @@ Now pi-sync behaviour should be: -Summary: If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. +Summary: +No new item ( new created after the last sync ) in a disabled calendar is propagated to the sync partner. Readonly items are synced and added/changed on the sync partner if it is not readonly on the sync partner. +If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. +Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars. |