author | zautrix <zautrix> | 2005-07-10 09:20:29 (UTC) |
---|---|---|
committer | zautrix <zautrix> | 2005-07-10 09:20:29 (UTC) |
commit | e8b6635ef7c98996f0415e6a77394569493ab151 (patch) (unidiff) | |
tree | 70fbf03e2ce62730fb8dddc288264c916e18d14e /bin/kdepim | |
parent | 2a3542ecc4eee8bb4b3d81fcf69e0cf97f07ff4a (diff) | |
download | kdepimpi-e8b6635ef7c98996f0415e6a77394569493ab151.zip kdepimpi-e8b6635ef7c98996f0415e6a77394569493ab151.tar.gz kdepimpi-e8b6635ef7c98996f0415e6a77394569493ab151.tar.bz2 |
version
-rw-r--r-- | bin/kdepim/WhatsNew.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt index 2fd89f1..3da24c5 100644 --- a/bin/kdepim/WhatsNew.txt +++ b/bin/kdepim/WhatsNew.txt | |||
@@ -1,66 +1,70 @@ | |||
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 ************ | ||
4 | |||
5 | |||
6 | |||
3 | ********** VERSION 2.1.15 ************ | 7 | ********** VERSION 2.1.15 ************ |
4 | 8 | ||
5 | Fixed two layout problems on the Z: | 9 | Fixed two layout problems on the Z: |
6 | 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. |
7 | 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. |
8 | 12 | ||
9 | 13 | ||
10 | ********** VERSION 2.1.14 ************ | 14 | ********** VERSION 2.1.14 ************ |
11 | 15 | ||
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. | 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. |
13 | Added a button to add a subtodo quickly. | 17 | Added a button to add a subtodo quickly. |
14 | 18 | ||
15 | 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 ). |
16 | 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. |
17 | 21 | ||
18 | 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. |
19 | 23 | ||
20 | Fixed pi-sync problems with the new multi calendar feature. | 24 | Fixed pi-sync problems with the new multi calendar feature. |
21 | Now pi-sync behaviour should be: | 25 | Now pi-sync behaviour should be: |
22 | 1) Local sends file request ( as usual ) | 26 | 1) Local sends file request ( as usual ) |
23 | 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. |
24 | 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 ). |
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. | 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. |
26 | 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. |
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. | 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. |
28 | 32 | ||
29 | Summary: | 33 | Summary: |
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. | 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. |
31 | 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. |
32 | 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. |
33 | 37 | ||
34 | ********** VERSION 2.1.13 ************ | 38 | ********** VERSION 2.1.13 ************ |
35 | 39 | ||
36 | Fixed a problem in KA/Pi search. | 40 | Fixed a problem in KA/Pi search. |
37 | Fixed some minor problems in KO/Pi. | 41 | Fixed some minor problems in KO/Pi. |
38 | 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. |
39 | 43 | ||
40 | Fixed memory usage problems in KA/Pi: | 44 | Fixed memory usage problems in KA/Pi: |
41 | When loading data KA/Pi did load the file data twice. | 45 | When loading data KA/Pi did load the file data twice. |
42 | Example: | 46 | Example: |
43 | A 600k file did consume 1200k memory during loading process. | 47 | A 600k file did consume 1200k memory during loading process. |
44 | 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. |
45 | 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. |
46 | This is fixed. | 50 | This is fixed. |
47 | Example: | 51 | Example: |
48 | 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. |
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. | 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. |
50 | Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process. | 54 | Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process. |
51 | Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. | 55 | Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. |
52 | The saving of data may be a bit slower now. | 56 | The saving of data may be a bit slower now. |
53 | 57 | ||
54 | Fixed memory usage problems in KO/Pi: | 58 | Fixed memory usage problems in KO/Pi: |
55 | When KO/Pi did save the data to file, it did not release the used buffers after saving. | 59 | When KO/Pi did save the data to file, it did not release the used buffers after saving. |
56 | The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. | 60 | The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. |
57 | This is fixed. | 61 | This is fixed. |
58 | Example: | 62 | Example: |
59 | When saving a 400k file KO/Pi do now use 400k less memory now. | 63 | When saving a 400k file KO/Pi do now use 400k less memory now. |
60 | 64 | ||
61 | Optimized memory usage in KO/Pi Agenda view: | 65 | Optimized memory usage in KO/Pi Agenda view: |
62 | KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view. | 66 | KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view. |
63 | These buffers were not made smaller (i.e. downsized) because of performance reasons. | 67 | These buffers were not made smaller (i.e. downsized) because of performance reasons. |
64 | The handling of these buffers are now much smarter: | 68 | The handling of these buffers are now much smarter: |
65 | Two (of six) buffers are removed completely. | 69 | Two (of six) buffers are removed completely. |
66 | The remaing four buffers are now downsized after not using the agenda view for 45 seconds. | 70 | The remaing four buffers are now downsized after not using the agenda view for 45 seconds. |