summaryrefslogtreecommitdiffabout
path: root/bin/kdepim
Unidiff
Diffstat (limited to 'bin/kdepim') (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/WhatsNew.txt5
1 files changed, 5 insertions, 0 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt
index d0b2880..f4b3ddb 100644
--- a/bin/kdepim/WhatsNew.txt
+++ b/bin/kdepim/WhatsNew.txt
@@ -1,98 +1,103 @@
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.19 ************
4
5Fixed a crash in journal view and a crash in setting a todo to stopped when KO/Pi saved the file when "stop todo" dialog was shown.
6Fixed a minor problem with the marcus bains line (whatever that is).
7
3********** VERSION 2.1.18 ************ 8********** VERSION 2.1.18 ************
4 9
5Pi-Sync mode: 10Pi-Sync mode:
6The "Write back file" status dialog was updated too often such that writing back the file on the Z was very slow. Fixed. 11The "Write back file" status dialog was updated too often such that writing back the file on the Z was very slow. Fixed.
7 12
8KO/Pi: 13KO/Pi:
9Fixed a layout problem on the Z 5500 with the calender box right of the location box in the event/todo editor. Thanks to Andrew, who found, reported and fixed this problem ( I did not get that problem - it was working on my 5500 ). 14Fixed a layout problem on the Z 5500 with the calender box right of the location box in the event/todo editor. Thanks to Andrew, who found, reported and fixed this problem ( I did not get that problem - it was working on my 5500 ).
10 15
11Fixed a problem when (imported or added from other applications) events or todos did have attachments. 16Fixed a problem when (imported or added from other applications) events or todos did have attachments.
12Fixed a really ugly and hidden problem in the management of the parent/child relationchip of todos. 17Fixed a really ugly and hidden problem in the management of the parent/child relationchip of todos.
13 18
14 19
15********** VERSION 2.1.17 ************ 20********** VERSION 2.1.17 ************
16 21
17KO/Pi: 22KO/Pi:
18Added option to display times in What's Next View on two lines. 23Added option to display times in What's Next View on two lines.
19(Useful for display on the Zaurus with 240x320 screen) 24(Useful for display on the Zaurus with 240x320 screen)
20Removed "Allday" for allday events of one day duration in What's Next View. 25Removed "Allday" for allday events of one day duration in What's Next View.
21Added date range for allday events of more than one day duration in What's Next View. 26Added date range for allday events of more than one day duration in What's Next View.
22Fixed two problems in the data importing from Outlook: 27Fixed two problems in the data importing from Outlook:
23 Fixed the duplicated import if the summary, location or description had whitespaces at the end. 28 Fixed the duplicated import if the summary, location or description had whitespaces at the end.
24 Fixed a problem importing certain recurrence rules. 29 Fixed a problem importing certain recurrence rules.
25 30
26A journal in an ics file may have no dtStart value (as files from KNotes, which stores its notes in an ics journal file). 31A journal in an ics file may have no dtStart value (as files from KNotes, which stores its notes in an ics journal file).
27If now a journal has no dtStart value the dtStart value is set to the created value of the journal when loading the file. That makes it possible to view and edit "notes" from KNotes. Simply add another Resource in KO/Pi which is a copy of the ics file from KNotes. You will find the "notes" in KO/Pi as a journal entry on the date you created it. 32If now a journal has no dtStart value the dtStart value is set to the created value of the journal when loading the file. That makes it possible to view and edit "notes" from KNotes. Simply add another Resource in KO/Pi which is a copy of the ics file from KNotes. You will find the "notes" in KO/Pi as a journal entry on the date you created it.
28 33
29And some minor fixes in KO/Pi. 34And some minor fixes in KO/Pi.
30 35
31Fixed a crash on the desktop when closing KO/Pi after accessing adressbook data (Linux + Windows ). 36Fixed a crash on the desktop when closing KO/Pi after accessing adressbook data (Linux + Windows ).
32 37
33 38
34********** VERSION 2.1.16 ************ 39********** VERSION 2.1.16 ************
35 40
36Fixed a problem with the menu bar in KO/Pi and using the "Menu" hardware key on the Zaurus. 41Fixed a problem with the menu bar in KO/Pi and using the "Menu" hardware key on the Zaurus.
37Added columns for datetime in todo view: Last modified, created and last modified subtodo 42Added columns for datetime in todo view: Last modified, created and last modified subtodo
38Fixed a bug in agenda view displaying recurring multiday events which are longer than two days. 43Fixed a bug in agenda view displaying recurring multiday events which are longer than two days.
39Made conflict detection up to 4 times faster. 44Made conflict detection up to 4 times faster.
40 45
41********** VERSION 2.1.15 ************ 46********** VERSION 2.1.15 ************
42 47
43Fixed two layout problems on the Z: 48Fixed two layout problems on the Z:
44Made the with of the newly added buttons on the Quick-Todo smaller. 49Made the with of the newly added buttons on the Quick-Todo smaller.
45Made listweek layout in 2 columns on the Z760 in portait screen and full menubar visible. 50Made listweek layout in 2 columns on the Z760 in portait screen and full menubar visible.
46 51
47 52
48********** VERSION 2.1.14 ************ 53********** VERSION 2.1.14 ************
49 54
50Added 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. 55Added 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.
51Added a button to add a subtodo quickly. 56Added a button to add a subtodo quickly.
52 57
53Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ). 58Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ).
54Added an option to change the layout of the list week to column mode. 59Added an option to change the layout of the list week to column mode.
55 60
56Fixed some usability problems in pi-sync mode by adding some progress information about file transfer. 61Fixed some usability problems in pi-sync mode by adding some progress information about file transfer.
57 62
58Fixed pi-sync problems with the new multi calendar feature. 63Fixed pi-sync problems with the new multi calendar feature.
59Now pi-sync behaviour should be: 64Now pi-sync behaviour should be:
601) Local sends file request ( as usual ) 651) Local sends file request ( as usual )
612) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars. 662) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars.
623) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ). 673) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ).
63 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. 68 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.
644) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote. 694) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote.
65 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. 70 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.
66 71
67Summary: 72Summary:
68No 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. 73No 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.
69If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. 74If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour.
70Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars. 75Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars.
71 76
72********** VERSION 2.1.13 ************ 77********** VERSION 2.1.13 ************
73 78
74Fixed a problem in KA/Pi search. 79Fixed a problem in KA/Pi search.
75Fixed some minor problems in KO/Pi. 80Fixed some minor problems in KO/Pi.
76Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. 81Added calendar selection possibility to the todo view popup and to the event/todo/journal editor.
77 82
78Fixed memory usage problems in KA/Pi: 83Fixed memory usage problems in KA/Pi:
79When loading data KA/Pi did load the file data twice. 84When loading data KA/Pi did load the file data twice.
80Example: 85Example:
81 A 600k file did consume 1200k memory during loading process. 86 A 600k file did consume 1200k memory during loading process.
82 This is fixed, it does now consume only 600k during loading process. 87 This is fixed, it does now consume only 600k during loading process.
83When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. 88When saving data KA/Pi did consume a lot of memory for the data parsing during the save process.
84This is fixed. 89This is fixed.
85Example: 90Example:
86 Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram. 91 Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram.
87 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. 92 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.
88 Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process. 93 Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process.
89Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. 94Note: The memory usage of KA/Pi after the data is loaded/saved has not changed.
90The saving of data may be a bit slower now. 95The saving of data may be a bit slower now.
91 96
92Fixed memory usage problems in KO/Pi: 97Fixed memory usage problems in KO/Pi:
93When KO/Pi did save the data to file, it did not release the used buffers after saving. 98When KO/Pi did save the data to file, it did not release the used buffers after saving.
94The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. 99The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation.
95This is fixed. 100This is fixed.
96Example: 101Example:
97 When saving a 400k file KO/Pi do now use 400k less memory now. 102 When saving a 400k file KO/Pi do now use 400k less memory now.
98 103