summaryrefslogtreecommitdiffabout
path: root/bin/kdepim/WhatsNew.txt
Unidiff
Diffstat (limited to 'bin/kdepim/WhatsNew.txt') (more/less context) (show whitespace changes)
-rw-r--r--bin/kdepim/WhatsNew.txt6
1 files changed, 6 insertions, 0 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt
index d6b2dc7..79de197 100644
--- a/bin/kdepim/WhatsNew.txt
+++ b/bin/kdepim/WhatsNew.txt
@@ -1,26 +1,32 @@
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.14 ************
4
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.
6Added a button to add a subtodo quickly.
7
8
3********** VERSION 2.1.13 ************ 9********** VERSION 2.1.13 ************
4 10
5Fixed a problem in KA/Pi search. 11Fixed a problem in KA/Pi search.
6Fixed some minor problems in KO/Pi. 12Fixed some minor problems in KO/Pi.
7Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. 13Added calendar selection possibility to the todo view popup and to the event/todo/journal editor.
8 14
9Fixed memory usage problems in KA/Pi: 15Fixed memory usage problems in KA/Pi:
10When loading data KA/Pi did load the file data twice. 16When loading data KA/Pi did load the file data twice.
11Example: 17Example:
12 A 600k file did consume 1200k memory during loading process. 18 A 600k file did consume 1200k memory during loading process.
13 This is fixed, it does now consume only 600k during loading process. 19 This is fixed, it does now consume only 600k during loading process.
14When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. 20When saving data KA/Pi did consume a lot of memory for the data parsing during the save process.
15This is fixed. 21This is fixed.
16Example: 22Example:
17 Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram. 23 Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram.
18 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. 24 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.
19 Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process. 25 Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process.
20Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. 26Note: The memory usage of KA/Pi after the data is loaded/saved has not changed.
21The saving of data may be a bit slower now. 27The saving of data may be a bit slower now.
22 28
23Fixed memory usage problems in KO/Pi: 29Fixed memory usage problems in KO/Pi:
24When KO/Pi did save the data to file, it did not release the used buffers after saving. 30When KO/Pi did save the data to file, it did not release the used buffers after saving.
25The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. 31The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation.
26This is fixed. 32This is fixed.