-rw-r--r-- | bin/kdepim/WhatsNew.txt | 7 |
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 @@ | |||
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.15 ************ | ||
4 | |||
5 | Fixed two layout problems on the Z: | ||
6 | Made the with of the newly added buttons on the Quick-Todo smaller. | ||
7 | Made 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 | ||
5 | 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. | 12 | 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. |
6 | Added a button to add a subtodo quickly. | 13 | Added a button to add a subtodo quickly. |
7 | 14 | ||
8 | Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ). | 15 | Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ). |
9 | Added an option to change the layout of the list week to column mode. | 16 | Added an option to change the layout of the list week to column mode. |
10 | 17 | ||
11 | Fixed some usability problems in pi-sync mode by adding some progress information about file transfer. | 18 | Fixed some usability problems in pi-sync mode by adding some progress information about file transfer. |
12 | 19 | ||
13 | Fixed pi-sync problems with the new multi calendar feature. | 20 | Fixed pi-sync problems with the new multi calendar feature. |
14 | Now pi-sync behaviour should be: | 21 | Now pi-sync behaviour should be: |
15 | 1) Local sends file request ( as usual ) | 22 | 1) Local sends file request ( as usual ) |
16 | 2) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars. | 23 | 2) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars. |
17 | 3) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ). | 24 | 3) 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. |
19 | 4) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote. | 26 | 4) 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 | ||
22 | Summary: | 29 | Summary: |
23 | 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. | 30 | 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. |
24 | If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. | 31 | If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. |
25 | Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars. | 32 | Well, 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 | ||
29 | Fixed a problem in KA/Pi search. | 36 | Fixed a problem in KA/Pi search. |
30 | Fixed some minor problems in KO/Pi. | 37 | Fixed some minor problems in KO/Pi. |
31 | Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. | 38 | Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. |
32 | 39 | ||
33 | Fixed memory usage problems in KA/Pi: | 40 | Fixed memory usage problems in KA/Pi: |
34 | When loading data KA/Pi did load the file data twice. | 41 | When loading data KA/Pi did load the file data twice. |
35 | Example: | 42 | Example: |
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. |
38 | When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. | 45 | When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. |
39 | This is fixed. | 46 | This is fixed. |
40 | Example: | 47 | Example: |
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. |
44 | Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. | 51 | Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. |
45 | The saving of data may be a bit slower now. | 52 | The saving of data may be a bit slower now. |
46 | 53 | ||
47 | Fixed memory usage problems in KO/Pi: | 54 | Fixed memory usage problems in KO/Pi: |
48 | When KO/Pi did save the data to file, it did not release the used buffers after saving. | 55 | When KO/Pi did save the data to file, it did not release the used buffers after saving. |
49 | The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. | 56 | The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. |
50 | This is fixed. | 57 | This is fixed. |