-rw-r--r-- | bin/kdepim/Zaurus-KDE_syncHowTo.txt | 45 |
1 files changed, 44 insertions, 1 deletions
diff --git a/bin/kdepim/Zaurus-KDE_syncHowTo.txt b/bin/kdepim/Zaurus-KDE_syncHowTo.txt index 90c6237..5aad5da 100644 --- a/bin/kdepim/Zaurus-KDE_syncHowTo.txt +++ b/bin/kdepim/Zaurus-KDE_syncHowTo.txt | |||
@@ -1,251 +1,294 @@ | |||
1 | 1 | ||
2 | Sync HowTo Zaurus <-> KDE | 2 | Sync HowTo Zaurus <-> KDE |
3 | 3 | ||
4 | NOTE: | 4 | NOTE: |
5 | CURRENTLY ONLY SYNCING OF CALENDAR DATA IS SUPPORTED! | 5 | CURRENTLY ONLY SYNCING OF CALENDAR DATA IS SUPPORTED! |
6 | 6 | ||
7 | This is a | 7 | This is a |
8 | Sync HowTo Zaurus <-> K-Desktop Environment(KDE) | 8 | Sync HowTo Zaurus <-> K-Desktop Environment(KDE) |
9 | using the KDE-Pim/Pi applications | 9 | using the KDE-Pim/Pi applications |
10 | KAddressbook/Pi (KA/Pi) and KOrganizer/Pi (KO/Pi) | 10 | KAddressbook/Pi (KA/Pi) and KOrganizer/Pi (KO/Pi) |
11 | on the Zaurus (Z). | 11 | on the Zaurus (Z). |
12 | 12 | ||
13 | You can now easily sync your Z with the | 13 | You can now easily sync your Z with the |
14 | PIM data of the KDE. | 14 | PIM data of the KDE. |
15 | (addressbook and calendar data). | 15 | (addressbook and calendar data). |
16 | You need to install the desktop versions | 16 | You need to install the desktop versions |
17 | of KA/Pi+KO/Pi on the desktop. | 17 | of KA/Pi+KO/Pi on the desktop. |
18 | You need KDE version 3.3.0 or higher on your desktop. | 18 | You need KDE version 3.3.0 or higher on your desktop. |
19 | You need KA/Pi+KO/Pi version 1.9.11 or higher on the desktop | 19 | You need KA/Pi+KO/Pi version 1.9.11 or higher on the desktop |
20 | and on the Z. | 20 | and on the Z. |
21 | 21 | ||
22 | NOTE: Almost the same procedure will make it possible to | 22 | NOTE: Almost the same procedure will make it possible to |
23 | sync KA/Pi+KO/Pi running on Windows with KDE via network. | 23 | sync KA/Pi+KO/Pi running on Windows with KDE via network. |
24 | 24 | ||
25 | The setup+sync procedure is: | 25 | The setup+sync procedure is: |
26 | 26 | ||
27 | 0) How the syncing works | ||
27 | 1) Installing KA/Pi+KO/Pi on the Z | 28 | 1) Installing KA/Pi+KO/Pi on the Z |
28 | 2) Installing desktop version of KA/Pi+KO/Pi on the desktop | 29 | 2) Installing desktop version of KA/Pi+KO/Pi on the desktop |
29 | 3) Connection your Z to the desktop via network | 30 | 3) Connection your Z to the desktop via network |
30 | (network connection can be set up via USB cable or (W)Lan | 31 | (network connection can be set up via USB cable or (W)Lan |
31 | 4) Configuring KA/Pi+KO/Pi on Z for Sync | 32 | 4) Configuring KA/Pi+KO/Pi on Z for Sync |
32 | 5) Enable remote sync in KA/Pi+KO/Pi on the desktop | 33 | 5) Enable remote sync in KA/Pi+KO/Pi on the desktop |
33 | 6) Sync | 34 | 6) Sync |
34 | 35 | ||
36 | ***************************************************** | ||
37 | 0) How the syncing works | ||
38 | ***************************************************** | ||
39 | |||
40 | After setting up everything, the following actions will | ||
41 | be performed when syncing: | ||
42 | User enables "remote pi-sync" on desktop. | ||
43 | User chooses "sync with configured desktop profile" on the Z. | ||
44 | Z sends sync request via network to configured IP/port/password. | ||
45 | KO/Pi on desktop detects sync request and syncs with KDE (configurable!). | ||
46 | A window pops up, that KO/Pi on desktop is in "remote syncing mode". | ||
47 | If a conflict occurs when syncing KO/PI<->KDE on the desktop, | ||
48 | automatically the newest entry is choosen. | ||
49 | (To avoid the need of user interaction) | ||
50 | KO/Pi on desktop sends synced file to Zaurus. | ||
51 | KO/Pi on desktop is in "waiting mode" to get synced file back. | ||
52 | Zaurus is syncing it's own calendar with the received file. | ||
53 | Here can be some user interaction needed, i.e. | ||
54 | if the sync profile is configured as | ||
55 | "ask for every entry on conflict" and a conflict occurs. | ||
56 | Zaurus sends back synced file to desktop. | ||
57 | Syncing on Zaurus is complete now. | ||
58 | KO/Pi on desktop gets back synced file. | ||
59 | KO/Pi on desktop removes all entries in its own calendar and | ||
60 | reloads the synced file. | ||
61 | KO/Pi on desktop syncs with KDE. | ||
62 | After syncing with KDE is finished, KO/Pi closes | ||
63 | the "remote syncing mode" window and displays | ||
64 | a "syncing complete" message in the headline. | ||
65 | |||
66 | The actual syncing KO/Pi on desktop <-> KDE is | ||
67 | performed by a small command line tool "kdecaldump", | ||
68 | which writes/reads the complete KDE calendar resources to | ||
69 | a file/from a file. | ||
70 | KO/Pi tags changed entries such that an unchanged entry | ||
71 | is not changed in KDE by kdecaldump. That is important for | ||
72 | calendar entries in KDE, stored in a "disconnected IMAP" calendar resource. | ||
73 | |||
74 | |||
75 | Same way is KA/Pi working. | ||
76 | |||
35 | 77 | ||
36 | ***************************************************** | 78 | ***************************************************** |
37 | 1) Installing KA/Pi+KO/Pi on the Z | 79 | 1) Installing KA/Pi+KO/Pi on the Z |
38 | ***************************************************** | 80 | ***************************************************** |
39 | 81 | ||
40 | Download latest version of KA/Pi+KO/Pi from | 82 | Download latest version of KA/Pi+KO/Pi from |
41 | http://sourceforge.net/projects/kdepimpi/ | 83 | http://sourceforge.net/projects/kdepimpi/ |
42 | Project KDE/Pim. | 84 | Project KDE/Pim. |
43 | Direct link is: | 85 | Direct link is: |
44 | http://sourceforge.net/project/showfiles.php?group_id=104103&package_id=112604 | 86 | http://sourceforge.net/project/showfiles.php?group_id=104103&package_id=112604 |
45 | Click on the version number to read the release notes/change log. | 87 | Click on the version number to read the release notes/change log. |
46 | Choose there the right precompiled package for your Z: | 88 | Choose there the right precompiled package for your Z: |
47 | For Sharp ROM | 89 | For Sharp ROM |
48 | -File: kdepim_1.x.xx_for_SharpROM.ipk.zip | 90 | -File: kdepim_1.x.xx_for_SharpROM.ipk.zip |
49 | For Open Zaurus ROM: | 91 | For Open Zaurus ROM: |
50 | -File: kdepim_1.x.xx_for_OZ-gcc3xx.ipk.zip | 92 | -File: kdepim_1.x.xx_for_OZ-gcc3xx.ipk.zip |
51 | If unsure, choose: | 93 | If unsure, choose: |
52 | -File: kdepim_1.x.xx_for_SharpROM.ipk.zip | 94 | -File: kdepim_1.x.xx_for_SharpROM.ipk.zip |
53 | 95 | ||
54 | Unzip the file and install the packages as usual on your Z. | 96 | Unzip the file and install the packages as usual on your Z. |
55 | In order to intstall KA/Pi+KO/Pi on your Z, | 97 | In order to intstall KA/Pi+KO/Pi on your Z, |
56 | you need to install the following files: | 98 | you need to install the following files: |
57 | kmicrokdelibs_1.x.xx_arm.ipk | 99 | kmicrokdelibs_1.x.xx_arm.ipk |
58 | kaddressbook_1.x.xx_arm.ipk | 100 | kaddressbook_1.x.xx_arm.ipk |
59 | korganizer_1.x.xx_arm.ipk | 101 | korganizer_1.x.xx_arm.ipk |
60 | 102 | ||
61 | ***************************************************** | 103 | ***************************************************** |
62 | 2) Installing desktop version of KA/Pi+KO/Pi on the desktop | 104 | 2) Installing desktop version of KA/Pi+KO/Pi on the desktop |
63 | ***************************************************** | 105 | ***************************************************** |
64 | 106 | ||
65 | Precompiled packages are available for SuSE 9.1. | 107 | Precompiled packages are available for SuSE 9.1. |
66 | Choose on the above download location: | 108 | Choose on the above download location: |
67 | File: KDE-Pim-Pi-1.9.10-SuSE9.1.i586.rpm | 109 | File: KDE-Pim-Pi-1.9.10-SuSE9.1.i586.rpm |
68 | Download file and install it on console with | 110 | Download file and install it on console with |
69 | su | 111 | su |
70 | rpm -ihv KDE-Pim-Pi-1.9.10-SuSE9.1.i586.rpm | 112 | rpm -ihv KDE-Pim-Pi-1.9.10-SuSE9.1.i586.rpm |
71 | 113 | ||
72 | NOTE for users of SuSE 9.1: | 114 | NOTE for users of SuSE 9.1: |
73 | You need KDE version 3.3.0 or higher on your desktop. | 115 | You need KDE version 3.3.0 or higher on your desktop. |
74 | Plese make an online update in SuSE (YAST), then update | 116 | Plese make an online update in SuSE (YAST), then update |
75 | your KDE to version 3.3.0 or higher. | 117 | your KDE to version 3.3.0 or higher. |
76 | You can find links to updated precompiled versions of KDE | 118 | You can find links to updated precompiled versions of KDE |
77 | for SuSE 9.1 on the SusE web site, | 119 | for SuSE 9.1 on the SusE web site, |
78 | a direct link is for example: | 120 | a direct link is for example: |
79 | ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.1 | 121 | ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.1 |
80 | HOWTO UPDATE KDE: | 122 | HOWTO UPDATE KDE: |
81 | Download there the packages in "base". | 123 | Download there the packages in "base". |
82 | And the needed package for your language in "internationalization". | 124 | And the needed package for your language in "internationalization". |
83 | Put all downloaded files in one "installation" directory. | 125 | Put all downloaded files in one "installation" directory. |
84 | Open console and go to the downloaded "installation" directory. | 126 | Open console and go to the downloaded "installation" directory. |
85 | Do there a | 127 | Do there a |
86 | su | 128 | su |
87 | and then perform a test for the update: | 129 | and then perform a test for the update: |
88 | rpm -Uhv --test *.rpm | 130 | rpm -Uhv --test *.rpm |
89 | 131 | ||
90 | If no dependencies are shown, you can do the actual update with | 132 | If no dependencies are shown, you can do the actual update with |
91 | rpm -Uhv *.rpm | 133 | rpm -Uhv *.rpm |
92 | 134 | ||
93 | If there are missing dependencies, you can resolve them by | 135 | If there are missing dependencies, you can resolve them by |
94 | - download the needed updated KDE package from the | 136 | - download the needed updated KDE package from the |
95 | "applications" or from the "development" folder on the server. | 137 | "applications" or from the "development" folder on the server. |
96 | - adding a needed rpm package from the SuSE install DVD | 138 | - adding a needed rpm package from the SuSE install DVD |
97 | - remove the package that has dependencies from your "installation" directory. | 139 | - remove the package that has dependencies from your "installation" directory. |
98 | 140 | ||
99 | Do the | 141 | Do the |
100 | rpm -Uhv --test *.rpm | 142 | rpm -Uhv --test *.rpm |
101 | until you get no dependencies and no errors, then do a | 143 | until you get no dependencies and no errors, then do a |
102 | rpm -Uhv *.rpm | 144 | rpm -Uhv *.rpm |
103 | Run | 145 | Run |
104 | SuSEconfig | 146 | SuSEconfig |
105 | after installing with rpm is finished. | 147 | after installing with rpm is finished. |
106 | Restart KDE. | 148 | Restart KDE. |
107 | 149 | ||
108 | ***************************************************** | 150 | ***************************************************** |
109 | 3) Connection your Z to the desktop via network | 151 | 3) Connection your Z to the desktop via network |
110 | (network connection can be set up via USB cable or (W)Lan | 152 | (network connection can be set up via USB cable or (W)Lan |
111 | ***************************************************** | 153 | ***************************************************** |
112 | 154 | ||
113 | a) Connection via network cable/(W)Lan cards | 155 | a) Connection via network cable/(W)Lan cards |
114 | Connect your desktop to the network. | 156 | Connect your desktop to the network. |
115 | Set up networking on the Z. | 157 | Set up networking on the Z. |
116 | Make sure, you can ping the desktop from Z. | 158 | Make sure, you can ping the desktop from Z. |
117 | b) Connection via USB cable:(is working for Z 7x0 and Z5500) | 159 | b) Connection via USB cable:(is working for Z 7x0 and Z5500) |
118 | (i) Open console on desktop and type | 160 | (i) Open console on desktop and type |
119 | su | 161 | su |
120 | tail -f /var/log/messages | 162 | tail -f /var/log/messages |
121 | (ii) Connect your Z with the USB cable to your desktop | 163 | (ii) Connect your Z with the USB cable to your desktop |
122 | You should get as output in the above console | 164 | You should get as output in the above console |
123 | something like this: | 165 | something like this: |
124 | ("BUG" is the name of the desktop computer!) | 166 | ("BUG" is the name of the desktop computer!) |
125 | Oct 26 12:49:37 BUG kernel: usb 2-2: new full speed USB device using address 2 | 167 | Oct 26 12:49:37 BUG kernel: usb 2-2: new full speed USB device using address 2 |
126 | Oct 26 12:49:37 BUG kernel: usb 2-2: Product: SL-C860 | 168 | Oct 26 12:49:37 BUG kernel: usb 2-2: Product: SL-C860 |
127 | Oct 26 12:49:37 BUG kernel: usb 2-2: Manufacturer: Sharp | 169 | Oct 26 12:49:37 BUG kernel: usb 2-2: Manufacturer: Sharp |
128 | Oct 26 12:49:37 BUG /etc/hotplug/usb.agent[22659]: need a device for this command | 170 | Oct 26 12:49:37 BUG /etc/hotplug/usb.agent[22659]: need a device for this command |
129 | Oct 26 12:49:43 BUG kernel: usb0: register usbnet at usb-0000:00:1d.0-2, Sharp Zaurus, PXA-2xx based | 171 | Oct 26 12:49:43 BUG kernel: usb0: register usbnet at usb-0000:00:1d.0-2, Sharp Zaurus, PXA-2xx based |
130 | Oct 26 12:49:43 BUG kernel: usbcore: registered new driver usbnet | 172 | Oct 26 12:49:43 BUG kernel: usbcore: registered new driver usbnet |
131 | You see in the 5. line ("BUG kernel: usb0: register"), that usb device usb0 is used. | 173 | You see in the 5. line ("BUG kernel: usb0: register"), that usb device usb0 is used. |
132 | (iii) Create a network startup entry in /etc/sysconfig/network | 174 | (iii) Create a network startup entry in /etc/sysconfig/network |
133 | Depending of the number X of the used usb device, create a file | 175 | Depending of the number X of the used usb device, create a file |
134 | /etc/sysconfig/network/ifcfg-usbX | 176 | /etc/sysconfig/network/ifcfg-usbX |
135 | (in our case /etc/sysconfig/network/ifcfg-usb0 ) | 177 | (in our case /etc/sysconfig/network/ifcfg-usb0 ) |
136 | with the following content: | 178 | with the following content: |
137 | # usbX config for Zaurus | 179 | # usbX config for Zaurus |
138 | IPADDR='192.168.129.200' | 180 | IPADDR='192.168.129.200' |
139 | NETMASK='255.255.255.0' | 181 | NETMASK='255.255.255.0' |
140 | NETWORK='192.168.129.0' | 182 | NETWORK='192.168.129.0' |
141 | BROADCAST='192.168.129.255' | 183 | BROADCAST='192.168.129.255' |
142 | STARTMODE='hotplug' | 184 | STARTMODE='hotplug' |
143 | (iv) Disconnect the Z and connect the Z again to the desktop. | 185 | (iv) Disconnect the Z and connect the Z again to the desktop. |
144 | Now you should be able to ping the Z from the desktop, try in console on desktop: | 186 | Now you should be able to ping the Z from the desktop, try in console on desktop: |
145 | ping 192.168.129.201 | 187 | ping 192.168.129.201 |
146 | Now you should be able to ping the desktop from the Z, try in console on Z: | 188 | Now you should be able to ping the desktop from the Z, try in console on Z: |
147 | ping 192.168.129.200 | 189 | ping 192.168.129.200 |
148 | 190 | ||
149 | Now you will get a network connection automatically, | 191 | Now you will get a network connection automatically, |
150 | if you connect your Z to the desktop via the USB cable. | 192 | if you connect your Z to the desktop via the USB cable. |
151 | 193 | ||
152 | 194 | ||
153 | In the following, we assume, that | 195 | In the following, we assume, that |
154 | the desktop has the IP address: 192.168.129.200 | 196 | the desktop has the IP address: 192.168.129.200 |
155 | and that | 197 | and that |
156 | the Z has the IP address: 192.168.129.201 | 198 | the Z has the IP address: 192.168.129.201 |
157 | 199 | ||
158 | ***************************************************** | 200 | ***************************************************** |
159 | 4) Configuring KA/Pi+KO/Pi on Z for Sync | 201 | 4) Configuring KA/Pi+KO/Pi on Z for Sync |
160 | ***************************************************** | 202 | ***************************************************** |
161 | 203 | ||
162 | Start KO/Pi on the Z. | 204 | Start KO/Pi on the Z. |
163 | Choose Menu: Synchronize - Configure | 205 | Choose Menu: Synchronize - Configure |
164 | Fill in name for "Local device name:", e.g. "Z760" | 206 | Fill in name for "Local device name:", e.g. "Z760" |
165 | Click on "New profile" | 207 | Click on "New profile" |
166 | Set name of "Profile:", e.g. "BUG". | 208 | Set name of "Profile:", e.g. "BUG". |
167 | (that is the above name of the desktop computer) | 209 | (that is the above name of the desktop computer) |
168 | Choose "Profile kind": Pi-Sync. | 210 | Choose "Profile kind": Pi-Sync. |
169 | Set "Password for remote access", e.g. "xyz" for | 211 | Set "Password for remote access", e.g. "xyz" for |
170 | Calendar and Addressbook. | 212 | Calendar and Addressbook. |
171 | Set Remote IP address to 192.168.129.200 for | 213 | Set Remote IP address to 192.168.129.200 for |
172 | Calendar and Addressbook. | 214 | Calendar and Addressbook. |
173 | (Note: That is the IP address of the desktop!). | 215 | (Note: That is the IP address of the desktop!). |
174 | The "Remote port number" is 9197/9198 for | 216 | The "Remote port number" is 9197/9198 for |
175 | Calendar and Addressbook. | 217 | Calendar and Addressbook. |
176 | You do not have to change the | 218 | You do not have to change the |
177 | "Remote port number" or any other settings. | 219 | "Remote port number" or any other settings. |
178 | Click "OK" button to save your settings. | 220 | Click "OK" button to save your settings. |
179 | 221 | ||
180 | Now you have configured KA/Pi+KO/Pi sync on the Z, | 222 | Now you have configured KA/Pi+KO/Pi sync on the Z, |
181 | no need to configure anything in KA/Pi. | 223 | no need to configure anything in KA/Pi. |
182 | 224 | ||
183 | 225 | ||
184 | ***************************************************** | 226 | ***************************************************** |
185 | 5) Enable remote sync in KA/Pi+KO/Pi on the desktop | 227 | 5) Enable remote sync in KA/Pi+KO/Pi on the desktop |
186 | ***************************************************** | 228 | ***************************************************** |
187 | 229 | ||
188 | Start KO/Pi on the desktop. | 230 | Start KO/Pi on the desktop. |
189 | Do a "test" sync with KDE, choose menu: | 231 | Do a "test" sync with KDE, choose menu: |
190 | Synchronize - KDE_Desktop | 232 | Synchronize - KDE_Desktop |
191 | After syncing, you should have the same data in KDE | 233 | After syncing, you should have the same data in KDE |
192 | and in KO/Pi. | 234 | and in KO/Pi. |
193 | NOTE: | 235 | NOTE: |
194 | The KO/Pi version 1.9.10 had the bug, that on the first | 236 | The KO/Pi version 1.9.10 had the bug, that on the first |
195 | sync with KDE, all data in KDE was deleted. | 237 | sync with KDE, all data in KDE was deleted. |
196 | DO NOT USE VERSION 1.9.10! | 238 | DO NOT USE VERSION 1.9.10! |
197 | 239 | ||
198 | The bevaviour on the first sync is | 240 | The bevaviour on the first sync is |
199 | (in versions >= 1.9.11) | 241 | (in versions >= 1.9.11) |
200 | that no data is deleted, the data in KO/Pi and in | 242 | that no data is deleted, the data in KO/Pi and in |
201 | KDE is merged into one calendar. | 243 | KDE is merged into one calendar. |
202 | 244 | ||
203 | When the first sync was ok, please choose menu: | 245 | When the first sync was ok, please choose menu: |
204 | Synchronize - Enable Pi-sync | 246 | Synchronize - Enable Pi-sync |
205 | Fill in the values for port ("9197" in our examle) | 247 | Fill in the values for port ("9197" in our examle) |
206 | and for the password ( "xyz" in our example) | 248 | and for the password ( "xyz" in our example) |
207 | that you did configure on the Z for that computer. | 249 | that you did configure on the Z for that computer. |
208 | Enable "Automatically start at application start" | 250 | Enable "Automatically start at application start" |
209 | and "Automatically sync with KDE-Desktop when receiving sync request" | 251 | and "Automatically sync with KDE-Desktop when receiving sync request" |
210 | by checking the two boxes. | 252 | by checking the two boxes. |
211 | Close KO/Pi. | 253 | Close KO/Pi. |
212 | 254 | ||
213 | Configure / test KA/Pi on the desktop in the same way. | 255 | Configure / test KA/Pi on the desktop in the same way. |
214 | Fill in the right value for the port (9198 in our examle) | 256 | Fill in the right value for the port (9198 in our examle) |
215 | in KA/Pi! | 257 | in KA/Pi! |
216 | 258 | ||
217 | ***************************************************** | 259 | ***************************************************** |
218 | 6) Sync | 260 | 6) Sync |
219 | ***************************************************** | 261 | ***************************************************** |
220 | 262 | ||
221 | After configuring everything as above, you have to do | 263 | After configuring everything as above, you have to do |
222 | the following, if you want to sync your Zaurus with KDE: | 264 | the following, if you want to sync your Zaurus with KDE: |
223 | (It syncs will all resources in KDE, that are not "readonly"). | 265 | (It syncs will all resources in KDE, that are not "readonly"). |
224 | 266 | ||
225 | Start KO/Pi on the desktop. | 267 | Start KO/Pi on the desktop. |
268 | If Kontact or KOrganizer is running, save the calendar! | ||
226 | Connect the Z with the USB cable to your desktop. | 269 | Connect the Z with the USB cable to your desktop. |
227 | (Or to the local network). | 270 | (Or to the local network). |
228 | Choose on the Z the menu: | 271 | Choose on the Z the menu: |
229 | Syncronize - <your name for the desktop sync profile> | 272 | Syncronize - <your name for the desktop sync profile> |
230 | ( that was "BUG" in our example ). | 273 | ( that was "BUG" in our example ). |
231 | That's all. | 274 | That's all. |
232 | 275 | ||
233 | Do the same with KA/Pi. | 276 | Do the same with KA/Pi. |
234 | 277 | ||
235 | NOTE: | 278 | NOTE: |
236 | If an appointment/addressee is created on the Z, it is added to the | 279 | If an appointment/addressee is created on the Z, it is added to the |
237 | standard resource in KDE. | 280 | standard resource in KDE. |
238 | 281 | ||
239 | If you have todos with subtodos in your calendar, you will get on | 282 | If you have todos with subtodos in your calendar, you will get on |
240 | every sync (after you restartet KOrganizer or Kontact in KDE) | 283 | every sync (after you restartet KOrganizer or Kontact in KDE) |
241 | the message "xx items changed on local", where | 284 | the message "xx items changed on local", where |
242 | xx is greater or equal to the number of todos. | 285 | xx is greater or equal to the number of todos. |
243 | That behaviour is caused by a bug in KDE. | 286 | That behaviour is caused by a bug in KDE. |
244 | (In KDE, everytime a subtodo is loaded, | 287 | (In KDE, everytime a subtodo is loaded, |
245 | it's "last modified" settings are set to the current time - ouch!) | 288 | it's "last modified" settings are set to the current time - ouch!) |
246 | I hope that bug will be fixed soon. | 289 | I hope I can fix this bug in KDE soon. |
247 | 290 | ||
248 | 291 | ||
249 | 292 | ||
250 | 293 | ||
251 | 294 | ||