-rw-r--r-- | bin/kdepim/WhatsNew.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt index 3da24c5..8127ef4 100644 --- a/bin/kdepim/WhatsNew.txt +++ b/bin/kdepim/WhatsNew.txt | |||
@@ -1,53 +1,53 @@ | |||
1 | Info about the changes in new versions of KDE-Pim/Pi | 1 | Info about the changes in new versions of KDE-Pim/Pi |
2 | 2 | ||
3 | ********** VERSION 2.1.16 ************ | 3 | ********** VERSION 2.1.16 ************ |
4 | 4 | ||
5 | 5 | Fixed a problem with the menu bar in KO/Pi and using the "Menu" hardware key on the Zaurus. | |
6 | 6 | ||
7 | ********** VERSION 2.1.15 ************ | 7 | ********** VERSION 2.1.15 ************ |
8 | 8 | ||
9 | Fixed two layout problems on the Z: | 9 | Fixed two layout problems on the Z: |
10 | Made the with of the newly added buttons on the Quick-Todo smaller. | 10 | Made the with of the newly added buttons on the Quick-Todo smaller. |
11 | Made listweek layout in 2 columns on the Z760 in portait screen and full menubar visible. | 11 | Made listweek layout in 2 columns on the Z760 in portait screen and full menubar visible. |
12 | 12 | ||
13 | 13 | ||
14 | ********** VERSION 2.1.14 ************ | 14 | ********** VERSION 2.1.14 ************ |
15 | 15 | ||
16 | Added 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. | 16 | Added 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. |
17 | Added a button to add a subtodo quickly. | 17 | Added a button to add a subtodo quickly. |
18 | 18 | ||
19 | Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ). | 19 | Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ). |
20 | Added an option to change the layout of the list week to column mode. | 20 | Added an option to change the layout of the list week to column mode. |
21 | 21 | ||
22 | Fixed some usability problems in pi-sync mode by adding some progress information about file transfer. | 22 | Fixed some usability problems in pi-sync mode by adding some progress information about file transfer. |
23 | 23 | ||
24 | Fixed pi-sync problems with the new multi calendar feature. | 24 | Fixed pi-sync problems with the new multi calendar feature. |
25 | Now pi-sync behaviour should be: | 25 | Now pi-sync behaviour should be: |
26 | 1) Local sends file request ( as usual ) | 26 | 1) Local sends file request ( as usual ) |
27 | 2) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars. | 27 | 2) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars. |
28 | 3) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ). | 28 | 3) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ). |
29 | 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. | 29 | 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. |
30 | 4) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote. | 30 | 4) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote. |
31 | 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. | 31 | 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. |
32 | 32 | ||
33 | Summary: | 33 | Summary: |
34 | 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. | 34 | 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. |
35 | If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. | 35 | If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. |
36 | Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars. | 36 | Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars. |
37 | 37 | ||
38 | ********** VERSION 2.1.13 ************ | 38 | ********** VERSION 2.1.13 ************ |
39 | 39 | ||
40 | Fixed a problem in KA/Pi search. | 40 | Fixed a problem in KA/Pi search. |
41 | Fixed some minor problems in KO/Pi. | 41 | Fixed some minor problems in KO/Pi. |
42 | Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. | 42 | Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. |
43 | 43 | ||
44 | Fixed memory usage problems in KA/Pi: | 44 | Fixed memory usage problems in KA/Pi: |
45 | When loading data KA/Pi did load the file data twice. | 45 | When loading data KA/Pi did load the file data twice. |
46 | Example: | 46 | Example: |
47 | A 600k file did consume 1200k memory during loading process. | 47 | A 600k file did consume 1200k memory during loading process. |
48 | This is fixed, it does now consume only 600k during loading process. | 48 | This is fixed, it does now consume only 600k during loading process. |
49 | When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. | 49 | When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. |
50 | This is fixed. | 50 | This is fixed. |
51 | Example: | 51 | Example: |
52 | Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram. | 52 | Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram. |
53 | 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. | 53 | 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. |