Hi Julien, Hi Andrej,

just to be clear, if the events are all-day it should read as DTSTART;VALUE=DATE:20130718 DTEND;VALUE=DATE:20130718

the VALUE=DATE parameter is mandatory.

cheers

Marten

Am 11.07.2013 18:52, schrieb Julien Métairie:

Hi Andrej,

Thank you for your (fast) answer.

I think it should not set any hour/minute, for example : BEGIN:VEVENT SUMMARY:Test event [...] DTSTART:20130718 DTEND:20130718 END:VEVENT

In this manner, the event would appear with no time at all, as shown in attached screenshot. When creating a new event, it is a good idea to pre-fill start/end times with business hours, but a "all-day" event is valid all the day long (birthdays, holiday, ...).

Julien

-------- Message original -------- Sujet: Re: [Inf-IT DAVcl] All day event considered as from midnight to midnight De : Andrej Lezo andrej.lezo@inf-it.com Pour : davclients@inf-it.com Date : 11/07/2013 17:46

...

Hi Julien, This will be changed in next version. "all day" checkbox will set time on default values - start and end of business day. Regards,

Andrej Lezo

"Julien Métairie" ruliane@ruliane.net napísal:

...

Hi "list",

When I tick the "All day" check box for an event, it is actually created as during from 0:00 to 0:00. Here is part of the ics file :

BEGIN:VEVENT SUMMARY:Test [...] DTSTART;TZID=Europe/Paris:20130712T000000 DTEND;TZID=Europe/Paris:20130712T000000 END:VEVENT

Is there a place where I can change this behavior ?

Julien

Hi all,

There seems to be some kind of confusion as to what the problem is and we are talking about two different issues here :) 1. Julien is reffering to the fact that when you try to change a timed event to an all-day event, what actually happens is that you create a timed event thats starts at 00:00 of the start day, and end at 00:00 of the end day. That is a bug we identified some time ago, CalDavZAP incorrectly interpreted the all-day checkbox, thinking it wasnt ticked, even if it was, thus beeing unable to create a proper all-day event. The issue should be solved in the latest RC (0.9.1), however is still present on the demo site, which has the 0.9.0 version. 2. What Andrej is reffering to, is the interface behaviour when unticking the all-day checkbox. In the 0.9.0, when you untick the checkbox, the time values are auto-filled with 00:00 times, which can lead to some debatable (although logical) behaviour. We changed this in the 0.9.1 version, so the times for start and end date are auto-filled from the globalCalendarStartOfBusiness and globalCalendarEndOfBusiness config variables.

My question therefore is, which CalDavZAP version are you using Julien?

Matej Mihalik

On 12-Jul-13 00:57, Ján Máté wrote:

Hi Marten & Julien,

On Jul 11, 2013, at 10:17 PM, Marten Gajda <marten@dmfs.org mailto:marten@dmfs.org> wrote:

...

just to be clear, if the events are all-day it should read as DTSTART;VALUE=DATE:20130718 DTEND;VALUE=DATE:20130718

the VALUE=DATE parameter is mandatory.

yes, we use this parameter

...

Am 11.07.2013 18:52, schrieb Julien Métairie:

...

I think it should not set any hour/minute, for example : BEGIN:VEVENT SUMMARY:Test event [...] DTSTART:20130718 DTEND:20130718 END:VEVENT

In this manner, the event would appear with no time at all, as shown in attached screenshot. When creating a new event, it is a good idea to pre-fill start/end times with business hours, but a "all-day" event is valid all the day long (birthdays, holiday, ...).

it is already fixed in the 0.9.1 rc1 ... and the start/end hours (about which Andrej talked) are set when you uncheck the "All day" checkbox (instead of 00:00, 00:00 in the next release we will use values from globalCalendarStartOfBusiness and globalCalendarEndOfBusiness settings).

JM

Hi,

Ok then, try out our newest RC, http://www.inf-it.com/CalDavZAP_0.9.1-rc1.zip and the problems should go away :)

Matej Mihalik

On 12-Jul-13 11:11, "Julien Métairie" wrote:

Hi Matej,

Yes, it is what I understood of Ján's message. I am using version 0.9.0.

Regards, Julien

On Fri, July 12, 2013 10:51, Matej Mihalik wrote:

...

Hi all,

There seems to be some kind of confusion as to what the problem is and we are talking about two different issues here :)

1. Julien is reffering to the fact that when you try to change a timed

event to an all-day event, what actually happens is that you create a timed event thats starts at 00:00 of the start day, and end at 00:00 of the end day. That is a bug we identified some time ago, CalDavZAP incorrectly interpreted the all-day checkbox, thinking it wasnt ticked, even if it was, thus beeing unable to create a proper all-day event. The issue should be solved in the latest RC (0.9.1), however is still present on the demo site, which has the 0.9.0 version. 2. What Andrej is reffering to, is the interface behaviour when unticking the all-day checkbox. In the 0.9.0, when you untick the checkbox, the time values are auto-filled with 00:00 times, which can lead to some debatable (although logical) behaviour. We changed this in the 0.9.1 version, so the times for start and end date are auto-filled from the globalCalendarStartOfBusiness and globalCalendarEndOfBusiness config variables.

My question therefore is, which CalDavZAP version are you using Julien?

Matej Mihalik

On 12-Jul-13 00:57, Ján Máté wrote:

...

Hi Marten & Julien,

On Jul 11, 2013, at 10:17 PM, Marten Gajda <marten@dmfs.org mailto:marten@dmfs.org> wrote:

...

just to be clear, if the events are all-day it should read as DTSTART;VALUE=DATE:20130718 DTEND;VALUE=DATE:20130718

the VALUE=DATE parameter is mandatory.

yes, we use this parameter

...

Am 11.07.2013 18:52, schrieb Julien Métairie:

...

I think it should not set any hour/minute, for example : BEGIN:VEVENT SUMMARY:Test event [...] DTSTART:20130718 DTEND:20130718 END:VEVENT

In this manner, the event would appear with no time at all, as shown in attached screenshot. When creating a new event, it is a good idea to pre-fill start/end times with business hours, but a "all-day" event is valid all the day long (birthdays, holiday, ...).

it is already fixed in the 0.9.1 rc1 ... and the start/end hours (about which Andrej talked) are set when you uncheck the "All day" checkbox (instead of 00:00, 00:00 in the next release we will use values from globalCalendarStartOfBusiness and globalCalendarEndOfBusiness settings).

JM

On Jul 12, 2013, at 1:48 PM, Jim Seymour jseymour@LinxNet.com wrote:

[snip]

...

2. What Andrej is reffering to, is the interface behaviour

when unticking the all-day checkbox. In the 0.9.0, when you untick the checkbox, the time values are auto-filled with 00:00 times, which can lead to some debatable (although logical) behaviour.

It is logical and I don't see how it could be debatable. If you un-check the all-day checkbox and give it no new time(s), then it has no time(s).

Then the question is why you want to uncheck the "All day" checkbox. An event with DATE value (instead of default DATE-TIME) is considered as all day event.

...

We changed this in the 0.9.1 version, so the times for start and end date are auto-filled from the globalCalendarStartOfBusiness and globalCalendarEndOfBusiness config variables.

[snip]

Which, in business terms, is "all day." That is not logical behaviour, IMO.

Unchecking the "All day" checkbox needs to add time to the interface and if it adds the default business start/end then the result is consistent (the event type is changed but the meaning is the same).

JM