On 11/04/2014 09:03:08, "Patrick Ohly" <patrick.ohly(a)intel.com> wrote:
On Thu, 2014-04-10 at 19:45 +0000, Emiliano Heyns wrote:
> On 10/04/2014 21:33:05, "Patrick Ohly" <patrick.ohly(a)intel.com>
>wrote:
> >The "sync" property lives in the intersection of data source and
>sync
> >source, so it *is* part of Xmn. I would even say that it is the most
> >important part of it, although there are others ("uri",
"syncFormat"
> >and
> >"forceSyncFormat").
> OK, I understand that. But then how should I understand the earlier
> "Nothing stops you from setting a "sync" property in one of the Xmn
> boxes. But these values are not used and therefore don't make sense
> there." when we were discussing how target-config fits into all of
>this?
You can set a "sync" value there. But SyncEvolution will not use it.
Instead it will take the "sync" value from the sync config used to
trigger the local sync and override the target-config's "sync" property
values accordingly.
OK, so setting 'sync' in the special target-config
SyncSource (Xmn) is
possible but useless. In all other SyncSources this is useful. I was
just thrown off by the "in one of the Xmn boxes", which I read as "in
any one of the Xmn boxes, at any line".
Emile