<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta content="text/html; charset=ISO-8859-15"
<body bgcolor="#ffffff" text="#000000">
Le 06/12/2010 21:29, Georg C. F. Greve a écrit :
<pre wrap="">Hi Alain,
On Monday 06 December 2010 20.54:08 Alain Abbas wrote:
<pre wrap="">i think me must have a tag deleted and a tag exceptionstartime or keep
the start-time in case of the exception is a deletion :
I am not quite sure whether I understood your suggestion correctly.
Currently, the proposal says that an exclusion without a subevent is a
deletion. If it contains a subevent, that subevent contains only the difference
towards the main even, all fields that are not specified remain unchanged.
Your proposal seems to be thinking of simultaneously changing a recurrence
exception and deleting it. This does not seem to make sense to me right now,
as deletion would also delete the changes.
but it s more simple to process all at the same level for alghorithm
as subevent Poom model in active sync is like that <br>
and the object model in outlook i think too <br>
if the deletion is in the same tag you have just a loop and a test .
if there are at different level you must have 2 loops with the risk
of error if <br>
a date is in the exclusion and in the subevent too <br>
So I must have misunderstood the idea.
Could you try to explain in more detail what you had in mind?
Kolab-format mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kolabfirstname.lastname@example.org">Kolabemail@example.com</a>
<a class="moz-txt-link-freetext" href="https://kolab.org/mailman/listinfo/kolab-format">https://kolab.org/mailman/listinfo/kolab-format</a>