author | zautrix <zautrix> | 2005-01-21 15:38:31 (UTC) |
---|---|---|
committer | zautrix <zautrix> | 2005-01-21 15:38:31 (UTC) |
commit | 4afdcfcac216b428ada79f4750cf7447e3175333 (patch) (unidiff) | |
tree | 8f70936ac23137c3f6fb00fce33edbfe3d821f59 /bin | |
parent | 234b9425bebd41b556277cdd94138fafecc32b45 (diff) | |
download | kdepimpi-4afdcfcac216b428ada79f4750cf7447e3175333.zip kdepimpi-4afdcfcac216b428ada79f4750cf7447e3175333.tar.gz kdepimpi-4afdcfcac216b428ada79f4750cf7447e3175333.tar.bz2 |
some fixes
-rw-r--r-- | bin/kdepim/SyncHowto.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bin/kdepim/SyncHowto.txt b/bin/kdepim/SyncHowto.txt index 64f6f14..b0473a1 100644 --- a/bin/kdepim/SyncHowto.txt +++ b/bin/kdepim/SyncHowto.txt | |||
@@ -1,281 +1,281 @@ | |||
1 | WARNING: | 1 | WARNING: |
2 | YOU MAY GET UNEXPECTED (I.E. WRONG) SYNCHRONIZATION RESULTS, | 2 | YOU MAY GET UNEXPECTED (I.E. WRONG) SYNCHRONIZATION RESULTS, |
3 | IF YOU CHANGE AN EVENT ON THE FIRST DEVICE AND SYNC IMMEDIATELY FROM | 3 | IF YOU CHANGE AN EVENT ON THE FIRST DEVICE AND SYNC IMMEDIATELY FROM |
4 | THE OTHER DEVICE WITH THIS DEVICE, IF THE CLOCKS OF THE TWO DEVICES | 4 | THE OTHER DEVICE WITH THIS DEVICE, IF THE CLOCKS OF THE TWO DEVICES |
5 | HAVE TOO MUCH DIFFERENCE. | 5 | HAVE TOO MUCH DIFFERENCE. |
6 | 6 | ||
7 | In other words: Please make sure, that the clocks of the devices | 7 | In other words: Please make sure, that the clocks of the devices |
8 | you want to sync have only a difference of some seconds! | 8 | you want to sync have only a difference of some seconds! |
9 | 9 | ||
10 | 10 | ||
11 | CONTENT: | 11 | CONTENT: |
12 | 12 | ||
13 | 0) How syncing works | 13 | 0) How syncing works |
14 | 1) Qick overview of settings | 14 | 1) Qick overview of settings |
15 | 2) Sync settings in sync dialog | 15 | 2) Sync settings in sync dialog |
16 | 3) Syncing background | 16 | 3) Syncing background |
17 | 4) Sync preferences | 17 | 4) Sync preferences |
18 | 5) How a filter works | 18 | 5) How a filter works |
19 | 6) Details about sync profile kinds | 19 | 6) Details about sync profile kinds |
20 | 20 | ||
21 | ************************************************************************* | 21 | ************************************************************************* |
22 | 0) How syncing works | 22 | 0) How syncing works |
23 | ************************************************************************* | 23 | ************************************************************************* |
24 | 24 | ||
25 | Note: | 25 | Note: |
26 | The recommended and easiest way to syncronize two devices where | 26 | The recommended and easiest way to syncronize two devices where |
27 | KO/Pi, KA/Pi or PWM/Pi is installed, is the profile kind "Pi-Sync". | 27 | KO/Pi, KA/Pi or PWM/Pi is installed, is the profile kind "Pi-Sync". |
28 | Details about that in 6) b). | 28 | Details about that in 6) b). |
29 | 29 | ||
30 | In KDE-Pim/Pi you can synchronize ( sync ) your calendar/addressbook/ | 30 | In KDE-Pim/Pi you can synchronize ( sync ) your calendar/addressbook/ |
31 | passwordfile with another calendar/addressbook/passwordfile, | 31 | passwordfile with another calendar/addressbook/passwordfile, |
32 | by syncing your (local) calendar/addressbook/passwordfile | 32 | by syncing your (local) calendar/addressbook/passwordfile |
33 | with a (remote) file. | 33 | with a (remote) file. |
34 | This remote file may on your local filesystem | 34 | This remote file may on your local filesystem |
35 | or on another (remote) device. | 35 | or on another (remote) device. |
36 | 36 | ||
37 | If you want to sync with another remote device, you have to create | 37 | If you want to sync with another remote device, you have to create |
38 | a sync profile. | 38 | a sync profile. |
39 | You have two choices for choosing the profil kind: | 39 | You have two choices for choosing the profil kind: |
40 | I) You can choose profile kind "Remote file" and specify a | 40 | I) You can choose profile kind "Remote file" and specify a |
41 | command line download/upload command ( like scp, ftp, ...) to | 41 | command line download/upload command ( like scp, ftp, ...) to |
42 | a) download the remote file to your local machine to a temp file | 42 | a) download the remote file to your local machine to a temp file |
43 | b) sync with this temp file | 43 | b) sync with this temp file |
44 | c) upload the synced file to the remote device | 44 | c) upload the synced file to the remote device |
45 | II) If you want to sync with a device, where KO/Pi( or KA/Pi, PWM/Pi) is | 45 | II) If you want to sync with a device, where KO/Pi( or KA/Pi, PWM/Pi) is |
46 | installed, you can easily get the remote file via network | 46 | installed, you can easily get the remote file via network |
47 | with the build in file transfer feature: | 47 | with the build in file transfer feature: |
48 | Choose profile kind "Pi-Sync" and | 48 | Choose profile kind "Pi-Sync" and |
49 | a) Start KO/Pi,KA/Pi or PWM/Pi on remote device and | 49 | a) Start KO/Pi,KA/Pi or PWM/Pi on remote device and |
50 | enable "Pi-Sync" on remote device with password and port. | 50 | enable "Pi-Sync" on remote device with password and port. |
51 | b) Specify password, port and IP address in your profile. | 51 | b) Specify password, port and IP address in your profile. |
52 | 52 | ||
53 | 53 | ||
54 | You can sync with your mobile phone as well. | 54 | You can sync with your mobile phone as well. |
55 | Everything is explained in more details below. | 55 | Everything is explained in more details below. |
56 | 56 | ||
57 | NOTE: | 57 | NOTE: |
58 | If you do not use profile kind "Pi-Sync", | 58 | If you do not use profile kind "Pi-Sync", |
59 | it is recommended to close | 59 | it is recommended to close |
60 | a running KO/Pi (KA/Pi, PWM/Pi) on the remote device. | 60 | a running KO/Pi (KA/Pi, PWM/Pi) on the remote device. |
61 | (Note: KO/Pi(KA/Pi, PWM/Pi) running on Zaurus with | 61 | (Note: KO/Pi(KA/Pi, PWM/Pi) running on Zaurus with |
62 | FastLoad enabled will never be closed!) | 62 | FastLoad enabled will never be closed!) |
63 | After syncing with a running KO/Pi on the remote device, | 63 | After syncing with a running KO/Pi on the remote device, |
64 | a "save" on the remote device will tell you that it needs to merge (sync). | 64 | a "save" on the remote device will tell you that it needs to merge (sync). |
65 | After merging (just a syncing with the changed file) | 65 | After merging (just a syncing with the changed file) |
66 | you will get the new data showing in remote KO/Pi. | 66 | you will get the new data showing in remote KO/Pi. |
67 | 67 | ||
68 | ************************************************************************* | 68 | ************************************************************************* |
69 | 1) Qick overview of settings | 69 | 1) Qick overview of settings |
70 | ************************************************************************* | 70 | ************************************************************************* |
71 | 71 | ||
72 | a) Open sync settings dialog (Menu Synchronize - Configure...) | 72 | a) Open sync settings dialog (Menu Synchronize - Configure...) |
73 | b) Give your device a unique name. | 73 | b) Give your device a unique name. |
74 | (unique in the set of all devices you want to sync with). | 74 | (unique in the set of all devices you want to sync with). |
75 | If you have already configured another devive and created | 75 | If you have already configured another devive and created |
76 | there a sync profile to sync with this device, give your device | 76 | there a sync profile to sync with this device, give your device |
77 | the same name as this sync profile! The same name is important, | 77 | the same name as this sync profile! The same name is important, |
78 | because it makes it possible to sync first A->B | 78 | because it makes it possible to sync first A->B |
79 | (A local device, that performs the sync, B remote device) | 79 | (A local device, that performs the sync, B remote device) |
80 | and then B->A. Such that the B->A sync knows about the | 80 | and then B->A. Such that the B->A sync knows about the |
81 | already performed A->B sync. | 81 | already performed A->B sync. |
82 | That means: It is unimportant if you sync A->B or B->A, | 82 | That means: It is unimportant if you sync A->B or B->A, |
83 | the devices A and B will be synced properly. | 83 | the devices A and B will be synced properly. |
84 | c) Create a new sync profile and give it a unique name. | 84 | c) Create a new sync profile and give it a unique name. |
85 | (unique in the set of all sync profiles on this device). | 85 | (unique in the set of all sync profiles on this device). |
86 | If you want to sync with a device, where KO/Pi is already installed | 86 | If you want to sync with a device, where KO/Pi is already installed |
87 | and which has a given unique device name, use this device name as | 87 | and which has a given unique device name, use this device name as |
88 | your profile name ( refer to b) ). | 88 | your profile name ( refer to b) ). |
89 | d) Coose the profile kind of your syncing method: | 89 | d) Choose the profile kind of your syncing method: |
90 | (i) Local file or | 90 | (i) Local file or |
91 | (ii) Pi-Sync or | 91 | (ii) Pi-Sync or |
92 | (iii) Remote file or | 92 | (iii) Remote file or |
93 | (iiii) Mobile Phone. | 93 | (iiii) Mobile Phone. |
94 | Detailed explanation in 6) | 94 | Detailed explanation in 6) |
95 | e) Choose the other profile options. | 95 | e) Choose the other profile options. |
96 | Detailed explanation in 2) | 96 | Detailed explanation in 2) |
97 | f) Close sync dialog with OK. | 97 | f) Close sync dialog with OK. |
98 | g) Sync. | 98 | g) Sync. |
99 | 99 | ||
100 | NOTE: | 100 | NOTE: |
101 | AFTER SYNCING THERE ARE "SYNC EVENTS" CREATED | 101 | AFTER SYNCING THERE ARE "SYNC EVENTS" CREATED |
102 | (OR UPDATED, IF IT ALREADY EXITS) FOR EACH SYNC PROFILE. | 102 | (OR UPDATED, IF IT ALREADY EXITS) FOR EACH SYNC PROFILE. |
103 | YOU MAY NOT DELETE OR CHANGE THESE EVENTS. | 103 | YOU MAY NOT DELETE OR CHANGE THESE EVENTS. |
104 | 104 | ||
105 | ************************************************************************* | 105 | ************************************************************************* |
106 | 2) Sync settings in sync dialog | 106 | 2) Sync settings in sync dialog |
107 | ************************************************************************* | 107 | ************************************************************************* |
108 | 108 | ||
109 | a) Local device name: | 109 | a) Local device name: |
110 | -> 1) b) | 110 | -> 1) b) |
111 | b) Profile: | 111 | b) Profile: |
112 | -> 1) c) | 112 | -> 1) c) |
113 | c) Multiple Sync options: Include in multiple sync: | 113 | c) Multiple Sync options: Include in multiple sync: |
114 | In the Synchronize menu, there is a multiple sync menu entry. | 114 | In the Synchronize menu, there is a multiple sync menu entry. |
115 | If you choose this menu entry, all user defined profiles with this | 115 | If you choose this menu entry, all user defined profiles with this |
116 | 'Include in multiple sync' option enabled will be synced | 116 | 'Include in multiple sync' option enabled will be synced |
117 | one after another. And this twice. This will take some time. | 117 | one after another. And this twice. This will take some time. |
118 | After that sync, on all devices should be the same data. | 118 | After that sync, on all devices should be the same data. |
119 | 119 | ||
120 | d)- j) Sync algo options: | 120 | d)- j) Sync algo options: |
121 | 121 | ||
122 | d) Ask for preferences before sync: | 122 | d) Ask for preferences before sync: |
123 | Check this to be asked for "Sync preferences" settings before each sync. | 123 | Check this to be asked for "Sync preferences" settings before each sync. |
124 | If the profile kind is "Pi-Sync" you will be asked to confirm | 124 | If the profile kind is "Pi-Sync" you will be asked to confirm |
125 | the "Pi-Sync" specific settings (Password,IP address, port number) | 125 | the "Pi-Sync" specific settings (Password,IP address, port number) |
126 | as well. That makes it possible to use that profile for a | 126 | as well. That makes it possible to use that profile for a |
127 | device that is connected via DHCP to the network and gets different | 127 | device that is connected via DHCP to the network and gets different |
128 | IP addresses when connecting to the network. | 128 | IP addresses when connecting to the network. |
129 | e) Sync preferences: | 129 | e) Sync preferences: |
130 | Choose here your sync preferences. | 130 | Choose here your sync preferences. |
131 | Details -> 4) | 131 | Details -> 4) |
132 | f) Show summary after sync: | 132 | f) Show summary after sync: |
133 | Check this to get a small summary dialog after sync | 133 | Check this to get a small summary dialog after sync |
134 | about number of added/changed/deleted events on local/remote. | 134 | about number of added/changed/deleted events on local/remote. |
135 | g) Apply filter when adding data to local: | 135 | g) Apply filter when adding data to local: |
136 | What is a filter? You can read this in -> 5) | 136 | What is a filter? You can read this in -> 5) |
137 | With this option you can specify a filter for events/contacts, | 137 | With this option you can specify a filter for events/contacts, |
138 | which should be added to the local database, because they are | 138 | which should be added to the local database, because they are |
139 | in the remote database and not in the local database. | 139 | in the remote database and not in the local database. |
140 | (Database = calendar file or addressbook file). | 140 | (Database = calendar file or addressbook file). |
141 | Note that the filter is NOT applied to the remote | 141 | Note that the filter is NOT applied to the remote |
142 | database before syncing. It is only applied to a particular | 142 | database before syncing. It is only applied to a particular |
143 | item which should be added to the local database. | 143 | item which should be added to the local database. |
144 | Well, but what is the difference? | 144 | Well, but what is the difference? |
145 | The differnce is: If the remote database AND the local database contain | 145 | The differnce is: If the remote database AND the local database contain |
146 | an already synced item, which does not match the filter, then this item is synced. | 146 | an already synced item, which does not match the filter, then this item is synced. |
147 | If the remote database contains an item which does not match the filter | 147 | If the remote database contains an item which does not match the filter |
148 | and the local database does not contain this item, then this item is not added | 148 | and the local database does not contain this item, then this item is not added |
149 | to the local database, but it is still in the remote database after syncing. | 149 | to the local database, but it is still in the remote database after syncing. |
150 | g) Write back synced data: | 150 | g) Write back synced data: |
151 | Uncheck this to update the local calendar only. | 151 | Uncheck this to update the local calendar only. |
152 | I.e. your local calendar is synced with the remote calendar | 152 | I.e. your local calendar is synced with the remote calendar |
153 | but nothing on the remote calendar is changed. | 153 | but nothing on the remote calendar is changed. |
154 | If you uncheck "Write back synced data", the settings | 154 | If you uncheck "Write back synced data", the settings |
155 | under h) and i) are ignored, of course. | 155 | under h) and i) are ignored, of course. |
156 | 156 | ||
157 | h) - j) Write back options: | 157 | h) - j) Write back options: |
158 | 158 | ||
159 | h) Write back (on remote) existing entries only: | 159 | h) Write back (on remote) existing entries only: |
160 | Check this to update the remote data only. | 160 | Check this to update the remote data only. |
161 | I.e. no data from yor local calendar/addressbook is added to the | 161 | I.e. no data from yor local calendar/addressbook is added to the |
162 | remote device. You may use this option to | 162 | remote device. You may use this option to |
163 | sync against some kind of "public calendar/addressbook" without | 163 | sync against some kind of "public calendar/addressbook" without |
164 | adding anything of your personal data. | 164 | adding anything of your personal data. |
165 | But in this case, you cannot add an item to the remoet device. | 165 | But in this case, you cannot add an item to the remoet device. |
166 | i) Apply filter when adding data to remote: | 166 | i) Apply filter when adding data to remote: |
167 | What is a filter? You can read this in -> 5) | 167 | What is a filter? You can read this in -> 5) |
168 | With this option you can specify a filter for events/contacts, | 168 | With this option you can specify a filter for events/contacts, |
169 | which should be added to the remote database, because they are | 169 | which should be added to the remote database, because they are |
170 | in the local database and not in the remote database. | 170 | in the local database and not in the remote database. |
171 | (Database = calendar file or addressbook file). | 171 | (Database = calendar file or addressbook file). |
172 | Note that the filter is NOT applied to the local | 172 | Note that the filter is NOT applied to the local |
173 | database before syncing. It is only applied to a particular | 173 | database before syncing. It is only applied to a particular |
174 | item of the local database which should be added to the remote database. | 174 | item of the local database which should be added to the remote database. |
175 | Well, but what is the difference? | 175 | Well, but what is the difference? |
176 | The differnce is: If the local database AND the remote database contain | 176 | The differnce is: If the local database AND the remote database contain |
177 | an already synced item, which does not match the filter, then this item is synced. | 177 | an already synced item, which does not match the filter, then this item is synced. |
178 | If the local database contains an item which does not match the filter | 178 | If the local database contains an item which does not match the filter |
179 | and the remote database does not contain this item, then this item is not added | 179 | and the remote database does not contain this item, then this item is not added |
180 | to the remote database, but it is still in the local database after syncing. | 180 | to the remote database, but it is still in the local database after syncing. |
181 | Example: | 181 | Example: |
182 | You have specified a calendar filter "only public events". | 182 | You have specified a calendar filter "only public events". |
183 | You specify this filter as the outgoing filter for syncing. | 183 | You specify this filter as the outgoing filter for syncing. |
184 | If there is an event in the local database which is not "public", but "private", | 184 | If there is an event in the local database which is not "public", but "private", |
185 | this event is not added to the remote database. | 185 | this event is not added to the remote database. |
186 | If there is an event in the local database and in the remote database which is | 186 | If there is an event in the local database and in the remote database which is |
187 | "private" (maybe added by someone else) then this event is synced and | 187 | "private" (maybe added by someone else) then this event is synced and |
188 | it is in the local database and in the remote database after syncing. | 188 | it is in the local database and in the remote database after syncing. |
189 | That means in particular you cannot remove an event from the remote | 189 | That means in particular you cannot remove an event from the remote |
190 | database but setting it to "private". | 190 | database but setting it to "private". |
191 | If you want to remove the event you can clone it, set it to private and delete the | 191 | If you want to remove the event you can clone it, set it to private and delete the |
192 | original event. Then the original event is deleted in the remote database after sync and | 192 | original event. Then the original event is deleted in the remote database after sync and |
193 | the cloned event is not added to the remote database, because it is private. | 193 | the cloned event is not added to the remote database, because it is private. |
194 | j) Write back (calendar) entries for time period only: | 194 | j) Write back (calendar) entries for time period only: |
195 | Check this to write back only calendar entries for a given time period. | 195 | Check this to write back only calendar entries for a given time period. |
196 | (Useful when syncing with mobile phones.) | 196 | (Useful when syncing with mobile phones.) |
197 | You can specify the date range in weeks for the weeks in the past to the weeks in the future. | 197 | You can specify the date range in weeks for the weeks in the past to the weeks in the future. |
198 | 198 | ||
199 | k) Profile kind: | 199 | k) Profile kind: |
200 | Details -> 6) | 200 | Details -> 6) |
201 | 201 | ||
202 | ************************************************************************* | 202 | ************************************************************************* |
203 | 3) Syncing background | 203 | 3) Syncing background |
204 | ************************************************************************* | 204 | ************************************************************************* |
205 | 205 | ||
206 | The same mentioned for calendars is valid for addressbooks as well. | 206 | The same mentioned for calendars is valid for addressbooks as well. |
207 | 207 | ||
208 | Synchronizing calendars ( i.e. files ) means, | 208 | Synchronizing calendars ( i.e. files ) means, |
209 | to merge two calendars in a useful way. | 209 | to merge two calendars in a useful way. |
210 | If the two calendars are completely different, | 210 | If the two calendars are completely different, |
211 | there is no problem, the resulting calendar contains | 211 | there is no problem, the resulting calendar contains |
212 | all data from the local and from the remote calendar. | 212 | all data from the local and from the remote calendar. |
213 | 213 | ||
214 | Problems will occur, if you have edited items | 214 | Problems will occur, if you have edited items |
215 | from the local calendar on the remote machine. | 215 | from the local calendar on the remote machine. |
216 | Then it could be, that items are in conflict. | 216 | Then it could be, that items are in conflict. |
217 | Two items are "in conflict", if they have the | 217 | Two items are "in conflict", if they have the |
218 | same unique ID (which get an item at time of | 218 | same unique ID (which get an item at time of |
219 | creation and owns it until it is deleted ) | 219 | creation and owns it until it is deleted ) |
220 | and they both are modified after the last | 220 | and they both are modified after the last |
221 | synchronization. | 221 | synchronization. |
222 | 222 | ||
223 | At first sync of two calendars there is no item deleted. | 223 | At first sync of two calendars there is no item deleted. |
224 | If the calendars are synced before and there is an item, | 224 | If the calendars are synced before and there is an item, |
225 | which is not edited after the last sync and is only | 225 | which is not edited after the last sync and is only |
226 | available in one calendar, then this item is deleted | 226 | available in one calendar, then this item is deleted |
227 | in this calendar. | 227 | in this calendar. |
228 | 228 | ||
229 | But when was the last synchronization between two calendars? | 229 | But when was the last synchronization between two calendars? |
230 | 230 | ||
231 | To know that, KO/Pi creates at first syncing | 231 | To know that, KO/Pi creates at first syncing |
232 | of two files an unique event "<profile name> - sync Event" | 232 | of two files an unique event "<profile name> - sync Event" |
233 | on the remote and the local calendar. | 233 | on the remote and the local calendar. |
234 | After syncing, the start time of this event is set | 234 | After syncing, the start time of this event is set |
235 | to the time of syncing. | 235 | to the time of syncing. |
236 | The event is read only and the user may not change it. | 236 | The event is read only and the user may not change it. |
237 | 237 | ||
238 | If two such files are synced, that both have an event | 238 | If two such files are synced, that both have an event |
239 | "<profile name> - sync Event" and the events have | 239 | "<profile name> - sync Event" and the events have |
240 | the same start time, then deleted items on the one calendar | 240 | the same start time, then deleted items on the one calendar |
241 | are deleted on the other as well. | 241 | are deleted on the other as well. |
242 | 242 | ||
243 | 243 | ||
244 | ************************************************************************* | 244 | ************************************************************************* |
245 | 4) Sync preferences | 245 | 4) Sync preferences |
246 | ************************************************************************* | 246 | ************************************************************************* |
247 | 247 | ||
248 | Two items are "in conflict", if they have the same unique ID | 248 | Two items are "in conflict", if they have the same unique ID |
249 | and they both are modified after the last synchronization. | 249 | and they both are modified after the last synchronization. |
250 | (Details -> 3) ). | 250 | (Details -> 3) ). |
251 | 251 | ||
252 | If an item is not modified after the last sync and | 252 | If an item is not modified after the last sync and |
253 | it is not found in the other calendar, it is deleted. | 253 | it is not found in the other calendar, it is deleted. |
254 | 254 | ||
255 | On the first sync, there is no item deleted. | 255 | On the first sync, there is no item deleted. |
256 | 256 | ||
257 | SYNC PREFERENCES: | 257 | SYNC PREFERENCES: |
258 | -Take local entry on conflict: | 258 | -Take local entry on conflict: |
259 | Takes the local entry on conflict. | 259 | Takes the local entry on conflict. |
260 | If it is the first sync, | 260 | If it is the first sync, |
261 | "Ask for every entry" | 261 | "Ask for every entry" |
262 | is chosen automatically, | 262 | is chosen automatically, |
263 | if this is selected. | 263 | if this is selected. |
264 | 264 | ||
265 | -Take remote entry on conflict: | 265 | -Take remote entry on conflict: |
266 | Takes the remote entry on conflict. | 266 | Takes the remote entry on conflict. |
267 | If it is the first sync, | 267 | If it is the first sync, |
268 | "Ask for every entry" | 268 | "Ask for every entry" |
269 | is chosen automatically, | 269 | is chosen automatically, |
270 | if this is selected. | 270 | if this is selected. |
271 | 271 | ||
272 | -Take newest entry on conflict: | 272 | -Take newest entry on conflict: |
273 | This takes the newest entry on conflict. | 273 | This takes the newest entry on conflict. |
274 | May be the most useful syncing mode. | 274 | May be the most useful syncing mode. |
275 | 275 | ||
276 | -Ask for every entry on conflict: | 276 | -Ask for every entry on conflict: |
277 | Pops up an event viewer dialog and | 277 | Pops up an event viewer dialog and |
278 | shows the two conflicting entries there. | 278 | shows the two conflicting entries there. |
279 | The user can chose, which entry he would like to take. | 279 | The user can chose, which entry he would like to take. |
280 | The button for the newest entry | 280 | The button for the newest entry |
281 | is automatically set as default button. | 281 | is automatically set as default button. |