1 files changed, 2 insertions, 0 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt
index 79de197..814c541 100644
--- a/bin/kdepim/WhatsNew.txt
+++ b/bin/kdepim/WhatsNew.txt
@@ -1,55 +1,57 @@
 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" ).
 ********** 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.
 This is fixed.
 Example:
  When saving a 400k file KO/Pi do now use 400k less memory now.
 Optimized memory usage in KO/Pi Agenda view:
 KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view.
 These buffers were not made smaller (i.e. downsized)  because of performance reasons.
 The handling of these buffers are now much smarter:
 Two (of six) buffers are removed completely.
 The remaing four buffers are now downsized after not using the agenda view for 45 seconds.
 Such that the memory usage of KO/Pi is smaller now in general ( because 2 buffers are removed) and is much smaller when not using the agenda view. That is very important when using fastload for KO/Pi.
 Worst case example ( for a maximum size agenda content):
  When resizing the agenda content to a large scale, KO/Pi did use 17Meg of mem ( and did not use less memory until it was stopped). Now KO/Pi is using on the same operation only 14.3 Meg of mem and after 45 seconds not using the agenda view it uses only 9.4 Meg of mem.
 When switching to an unused Agenda view now KO/Pi is upizing the buffers again. This takes less than a second. Such that switching to Agenda view (after not using it for more than 45 seconds) is now a bit slower. 
 Summary:
 Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus.
 ********** VERSION 2.1.12 ************
 KO/Pi:
 Many small usability fixes, e.g. rearranged the popup menus such that they are better to use on the Zaurus.

diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt index 79de197..814c541 100644 --- a/bin/kdepim/WhatsNew.txt +++ b/bin/kdepim/WhatsNew.txt
@@ -1,55 +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.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" ).
		9
8		10
9	******** VERSION 2.1.13 **********	11	******** VERSION 2.1.13 **********
10		12
11	Fixed a problem in KA/Pi search.	13	Fixed a problem in KA/Pi search.
12	Fixed some minor problems in KO/Pi.	14	Fixed some minor problems in KO/Pi.
13	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.
14		16
15	Fixed memory usage problems in KA/Pi:	17	Fixed memory usage problems in KA/Pi:
16	When loading data KA/Pi did load the file data twice.	18	When loading data KA/Pi did load the file data twice.
17	Example:	19	Example:
18	A 600k file did consume 1200k memory during loading process.	20	A 600k file did consume 1200k memory during loading process.
19	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.
20	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.
21	This is fixed.	23	This is fixed.
22	Example:	24	Example:
23	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.
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.	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.
25	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.
26	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.
27	The saving of data may be a bit slower now.	29	The saving of data may be a bit slower now.
28		30
29	Fixed memory usage problems in KO/Pi:	31	Fixed memory usage problems in KO/Pi:
30	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.
31	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.
32	This is fixed.	34	This is fixed.
33	Example:	35	Example:
34	When saving a 400k file KO/Pi do now use 400k less memory now.	36	When saving a 400k file KO/Pi do now use 400k less memory now.
35		37
36	Optimized memory usage in KO/Pi Agenda view:	38	Optimized memory usage in KO/Pi Agenda view:
37	KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view.	39	KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view.
38	These buffers were not made smaller (i.e. downsized) because of performance reasons.	40	These buffers were not made smaller (i.e. downsized) because of performance reasons.
39	The handling of these buffers are now much smarter:	41	The handling of these buffers are now much smarter:
40	Two (of six) buffers are removed completely.	42	Two (of six) buffers are removed completely.
41	The remaing four buffers are now downsized after not using the agenda view for 45 seconds.	43	The remaing four buffers are now downsized after not using the agenda view for 45 seconds.
42	Such that the memory usage of KO/Pi is smaller now in general ( because 2 buffers are removed) and is much smaller when not using the agenda view. That is very important when using fastload for KO/Pi.	44	Such that the memory usage of KO/Pi is smaller now in general ( because 2 buffers are removed) and is much smaller when not using the agenda view. That is very important when using fastload for KO/Pi.
43		45
44	Worst case example ( for a maximum size agenda content):	46	Worst case example ( for a maximum size agenda content):
45	When resizing the agenda content to a large scale, KO/Pi did use 17Meg of mem ( and did not use less memory until it was stopped). Now KO/Pi is using on the same operation only 14.3 Meg of mem and after 45 seconds not using the agenda view it uses only 9.4 Meg of mem.	47	When resizing the agenda content to a large scale, KO/Pi did use 17Meg of mem ( and did not use less memory until it was stopped). Now KO/Pi is using on the same operation only 14.3 Meg of mem and after 45 seconds not using the agenda view it uses only 9.4 Meg of mem.
46		48
47	When switching to an unused Agenda view now KO/Pi is upizing the buffers again. This takes less than a second. Such that switching to Agenda view (after not using it for more than 45 seconds) is now a bit slower.	49	When switching to an unused Agenda view now KO/Pi is upizing the buffers again. This takes less than a second. Such that switching to Agenda view (after not using it for more than 45 seconds) is now a bit slower.
48		50
49	Summary:	51	Summary:
50	Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus.	52	Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus.
51		53
52	******** VERSION 2.1.12 **********	54	******** VERSION 2.1.12 **********
53		55
54	KO/Pi:	56	KO/Pi:
55	Many small usability fixes, e.g. rearranged the popup menus such that they are better to use on the Zaurus.	57	Many small usability fixes, e.g. rearranged the popup menus such that they are better to use on the Zaurus.