summaryrefslogtreecommitdiffabout
Unidiff
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/WhatsNew.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt
index c0d63e5..368f379 100644
--- a/bin/kdepim/WhatsNew.txt
+++ b/bin/kdepim/WhatsNew.txt
@@ -1,66 +1,70 @@
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.17 ************
4
5
6
3********** VERSION 2.1.16 ************ 7********** VERSION 2.1.16 ************
4 8
5Fixed a problem with the menu bar in KO/Pi and using the "Menu" hardware key on the Zaurus. 9Fixed a problem with the menu bar in KO/Pi and using the "Menu" hardware key on the Zaurus.
6Added columns for datetime in todo view: Last modified, created and last modified subtodo 10Added columns for datetime in todo view: Last modified, created and last modified subtodo
7Fixed a bug in agenda view displaying recurring multiday events which are longer than two days. 11Fixed a bug in agenda view displaying recurring multiday events which are longer than two days.
8Made conflict detection up to 4 times faster. 12Made conflict detection up to 4 times faster.
9 13
10********** VERSION 2.1.15 ************ 14********** VERSION 2.1.15 ************
11 15
12Fixed two layout problems on the Z: 16Fixed two layout problems on the Z:
13Made the with of the newly added buttons on the Quick-Todo smaller. 17Made the with of the newly added buttons on the Quick-Todo smaller.
14Made listweek layout in 2 columns on the Z760 in portait screen and full menubar visible. 18Made listweek layout in 2 columns on the Z760 in portait screen and full menubar visible.
15 19
16 20
17********** VERSION 2.1.14 ************ 21********** VERSION 2.1.14 ************
18 22
19Added 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. 23Added 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.
20Added a button to add a subtodo quickly. 24Added a button to add a subtodo quickly.
21 25
22Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ). 26Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ).
23Added an option to change the layout of the list week to column mode. 27Added an option to change the layout of the list week to column mode.
24 28
25Fixed some usability problems in pi-sync mode by adding some progress information about file transfer. 29Fixed some usability problems in pi-sync mode by adding some progress information about file transfer.
26 30
27Fixed pi-sync problems with the new multi calendar feature. 31Fixed pi-sync problems with the new multi calendar feature.
28Now pi-sync behaviour should be: 32Now pi-sync behaviour should be:
291) Local sends file request ( as usual ) 331) Local sends file request ( as usual )
302) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars. 342) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars.
313) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ). 353) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ).
32 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. 36 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.
334) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote. 374) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote.
34 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. 38 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.
35 39
36Summary: 40Summary:
37No 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. 41No 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.
38If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. 42If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour.
39Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars. 43Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars.
40 44
41********** VERSION 2.1.13 ************ 45********** VERSION 2.1.13 ************
42 46
43Fixed a problem in KA/Pi search. 47Fixed a problem in KA/Pi search.
44Fixed some minor problems in KO/Pi. 48Fixed some minor problems in KO/Pi.
45Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. 49Added calendar selection possibility to the todo view popup and to the event/todo/journal editor.
46 50
47Fixed memory usage problems in KA/Pi: 51Fixed memory usage problems in KA/Pi:
48When loading data KA/Pi did load the file data twice. 52When loading data KA/Pi did load the file data twice.
49Example: 53Example:
50 A 600k file did consume 1200k memory during loading process. 54 A 600k file did consume 1200k memory during loading process.
51 This is fixed, it does now consume only 600k during loading process. 55 This is fixed, it does now consume only 600k during loading process.
52When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. 56When saving data KA/Pi did consume a lot of memory for the data parsing during the save process.
53This is fixed. 57This is fixed.
54Example: 58Example:
55 Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram. 59 Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram.
56 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. 60 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.
57 Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process. 61 Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process.
58Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. 62Note: The memory usage of KA/Pi after the data is loaded/saved has not changed.
59The saving of data may be a bit slower now. 63The saving of data may be a bit slower now.
60 64
61Fixed memory usage problems in KO/Pi: 65Fixed memory usage problems in KO/Pi:
62When KO/Pi did save the data to file, it did not release the used buffers after saving. 66When KO/Pi did save the data to file, it did not release the used buffers after saving.
63The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. 67The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation.
64This is fixed. 68This is fixed.
65Example: 69Example:
66 When saving a 400k file KO/Pi do now use 400k less memory now. 70 When saving a 400k file KO/Pi do now use 400k less memory now.