summaryrefslogtreecommitdiffabout
Unidiff
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/WhatsNew.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt
index 2ce78c7..2fd89f1 100644
--- a/bin/kdepim/WhatsNew.txt
+++ b/bin/kdepim/WhatsNew.txt
@@ -1,50 +1,57 @@
1Info about the changes in new versions of KDE-Pim/Pi 1Info about the changes in new versions of KDE-Pim/Pi
2 2
3********** VERSION 2.1.15 ************
4
5Fixed two layout problems on the Z:
6Made the with of the newly added buttons on the Quick-Todo smaller.
7Made listweek layout in 2 columns on the Z760 in portait screen and full menubar visible.
8
9
3********** VERSION 2.1.14 ************ 10********** VERSION 2.1.14 ************
4 11
5Added some buttons to the KO/Pi Quick-todo line to make it possible to quickly access some todo view layout settings like display all flat/open/close and hide/show running/done. 12Added some buttons to the KO/Pi Quick-todo line to make it possible to quickly access some todo view layout settings like display all flat/open/close and hide/show running/done.
6Added a button to add a subtodo quickly. 13Added a button to add a subtodo quickly.
7 14
8Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ). 15Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ).
9Added an option to change the layout of the list week to column mode. 16Added an option to change the layout of the list week to column mode.
10 17
11Fixed some usability problems in pi-sync mode by adding some progress information about file transfer. 18Fixed some usability problems in pi-sync mode by adding some progress information about file transfer.
12 19
13Fixed pi-sync problems with the new multi calendar feature. 20Fixed pi-sync problems with the new multi calendar feature.
14Now pi-sync behaviour should be: 21Now pi-sync behaviour should be:
151) Local sends file request ( as usual ) 221) Local sends file request ( as usual )
162) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars. 232) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars.
173) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ). 243) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ).
18 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. 25 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.
194) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote. 264) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote.
20 If the data which remote receives contains entries which are on disabled calendars on remote this entries are updated and not added as duplicates to the default calendar. 27 If the data which remote receives contains entries which are on disabled calendars on remote this entries are updated and not added as duplicates to the default calendar.
21 28
22Summary: 29Summary:
23No 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. 30No 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.
24If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. 31If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour.
25Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars. 32Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars.
26 33
27********** VERSION 2.1.13 ************ 34********** VERSION 2.1.13 ************
28 35
29Fixed a problem in KA/Pi search. 36Fixed a problem in KA/Pi search.
30Fixed some minor problems in KO/Pi. 37Fixed some minor problems in KO/Pi.
31Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. 38Added calendar selection possibility to the todo view popup and to the event/todo/journal editor.
32 39
33Fixed memory usage problems in KA/Pi: 40Fixed memory usage problems in KA/Pi:
34When loading data KA/Pi did load the file data twice. 41When loading data KA/Pi did load the file data twice.
35Example: 42Example:
36 A 600k file did consume 1200k memory during loading process. 43 A 600k file did consume 1200k memory during loading process.
37 This is fixed, it does now consume only 600k during loading process. 44 This is fixed, it does now consume only 600k during loading process.
38When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. 45When saving data KA/Pi did consume a lot of memory for the data parsing during the save process.
39This is fixed. 46This is fixed.
40Example: 47Example:
41 Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram. 48 Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram.
42 When saving KA/Pi did consume 28.6 Meg of Ram. That causes a crash on the Zaurus because there was no memeory left in the system. 49 When saving KA/Pi did consume 28.6 Meg of Ram. That causes a crash on the Zaurus because there was no memeory left in the system.
43 Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process. 50 Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process.
44Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. 51Note: The memory usage of KA/Pi after the data is loaded/saved has not changed.
45The saving of data may be a bit slower now. 52The saving of data may be a bit slower now.
46 53
47Fixed memory usage problems in KO/Pi: 54Fixed memory usage problems in KO/Pi:
48When KO/Pi did save the data to file, it did not release the used buffers after saving. 55When KO/Pi did save the data to file, it did not release the used buffers after saving.
49The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. 56The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation.
50This is fixed. 57This is fixed.