| -rw-r--r-- | bin/kdepim/WhatsNew.txt | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt index aa4a89a..8fab725 100644 --- a/bin/kdepim/WhatsNew.txt +++ b/bin/kdepim/WhatsNew.txt @@ -1,34 +1,46 @@ 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", shift+q or ctrl +q ). Added an option to change the layout of the list week to column mode. +Fixed some usability problems in pi-sync mode by adding some progress information about file transfer. + +Fixed pi-sync problems with the new multi calendar feature. +Now pi-sync behaviour should be: +1) Local sends file request ( as usual ) +2) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars. +3) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ). +4) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote. + 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. + +Summary: If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. + ********** 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. |