1 files changed, 2 insertions, 2 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt
index 814c541..aa4a89a 100644
--- a/bin/kdepim/WhatsNew.txt
+++ b/bin/kdepim/WhatsNew.txt
@@ -1,33 +1,33 @@
 Info about the changes in new versions of KDE-Pim/Pi
 ********** VERSION 2.1.14 ************
 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.
 Added a button to add a subtodo quickly.
-Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q" ).
+Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ).
+Added an option to change the layout of the list week to column mode.
 ********** VERSION 2.1.13 ************
 Fixed a problem in KA/Pi search.
 Fixed some minor problems in KO/Pi.
 Added calendar selection possibility to the todo view popup and to the event/todo/journal editor.
 Fixed memory usage problems in KA/Pi:
 When loading data KA/Pi did load the file data twice.
 Example:
  A 600k file did consume 1200k memory during loading process.
  This is fixed, it does now consume only  600k during loading process.
 When saving data KA/Pi did consume a lot of memory for the data parsing during the save process.
 This is fixed.
 Example:
  Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram.
  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.
  Now  KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process. 
 Note: The memory usage of KA/Pi after the data is loaded/saved has not changed.
 The saving of data may be a bit slower now.
 Fixed memory usage problems in KO/Pi:
 When KO/Pi did save the data to file, it did not release the used buffers after saving.
 The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation.

diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt index 814c541..aa4a89a 100644 --- a/bin/kdepim/WhatsNew.txt +++ b/bin/kdepim/WhatsNew.txt
@@ -1,33 +1,33 @@
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.14 **********	3	******** VERSION 2.1.14 **********
4		4
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.	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.
6	Added a button to add a subtodo quickly.	6	Added a button to add a subtodo quickly.
7		7
8	Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q" ).	8	Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ).
9		9	Added an option to change the layout of the list week to column mode.
10		10
11	******** VERSION 2.1.13 **********	11	******** VERSION 2.1.13 **********
12		12
13	Fixed a problem in KA/Pi search.	13	Fixed a problem in KA/Pi search.
14	Fixed some minor problems in KO/Pi.	14	Fixed some minor problems in KO/Pi.
15	Added calendar selection possibility to the todo view popup and to the event/todo/journal editor.	15	Added calendar selection possibility to the todo view popup and to the event/todo/journal editor.
16		16
17	Fixed memory usage problems in KA/Pi:	17	Fixed memory usage problems in KA/Pi:
18	When loading data KA/Pi did load the file data twice.	18	When loading data KA/Pi did load the file data twice.
19	Example:	19	Example:
20	A 600k file did consume 1200k memory during loading process.	20	A 600k file did consume 1200k memory during loading process.
21	This is fixed, it does now consume only 600k during loading process.	21	This is fixed, it does now consume only 600k during loading process.
22	When saving data KA/Pi did consume a lot of memory for the data parsing during the save process.	22	When saving data KA/Pi did consume a lot of memory for the data parsing during the save process.
23	This is fixed.	23	This is fixed.
24	Example:	24	Example:
25	Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram.	25	Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram.
26	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.	26	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.
27	Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process.	27	Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process.
28	Note: The memory usage of KA/Pi after the data is loaded/saved has not changed.	28	Note: The memory usage of KA/Pi after the data is loaded/saved has not changed.
29	The saving of data may be a bit slower now.	29	The saving of data may be a bit slower now.
30		30
31	Fixed memory usage problems in KO/Pi:	31	Fixed memory usage problems in KO/Pi:
32	When KO/Pi did save the data to file, it did not release the used buffers after saving.	32	When KO/Pi did save the data to file, it did not release the used buffers after saving.
33	The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation.	33	The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation.