I've tested this on the online example:
http://www.telerik.com/demos/aspnet/prometheus/Scheduler/Examples/BlackPearl/DefaultCS.aspx
Double click on the all day area at the top, go to advanced enter mode, enter 3/27/2007 for the start day and 3/29/2007 for the end date and click insert. Notice that if you look at the day view for 3/27/2007 and 3/28/2007 the appointment is shown, but it is not shown on 3/29/2007.
Now, if you double click in the time area (say 10:00 AM) and go to the advanced mode, enter 3/27/2007 for the start day and 3/29/2007 for the end day, then click the all day checkbox, and then click insert. Now notice that this appointment will show up on all 3 days.
It seems that there is a problem with using the All Day portion of the calendar to enter appointments. Has anyone else seen this?
Thanks
http://www.telerik.com/demos/aspnet/prometheus/Scheduler/Examples/BlackPearl/DefaultCS.aspx
Double click on the all day area at the top, go to advanced enter mode, enter 3/27/2007 for the start day and 3/29/2007 for the end date and click insert. Notice that if you look at the day view for 3/27/2007 and 3/28/2007 the appointment is shown, but it is not shown on 3/29/2007.
Now, if you double click in the time area (say 10:00 AM) and go to the advanced mode, enter 3/27/2007 for the start day and 3/29/2007 for the end day, then click the all day checkbox, and then click insert. Now notice that this appointment will show up on all 3 days.
It seems that there is a problem with using the All Day portion of the calendar to enter appointments. Has anyone else seen this?
Thanks
1 Answer, 1 is accepted
0
Hi Ryan,
RadScheduler creates Appointments differently depending on the Time Slot that is used.
In case an Appointment is created in the All Day Slot, RadScheduelr presumes that the Appointment will be no less than exactly one day long. Then it extends it depending on the specified End Date.
When an Appointment is created in a normal Time Slot, RadScheduler knows that the Appointment will last from x to y hour on the same day. Choosing All Day Event will reset the Start and End Hours, hence the Appointment will last zero days. RadScheduler automatically adds one day just to fix this inconsistency.
If you try the second case, and then edit the Appointment, you will see that one day has been added to the End Date, although you have entered the day before when creating the Appointment.
All the best,
Simon
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
RadScheduler creates Appointments differently depending on the Time Slot that is used.
In case an Appointment is created in the All Day Slot, RadScheduelr presumes that the Appointment will be no less than exactly one day long. Then it extends it depending on the specified End Date.
When an Appointment is created in a normal Time Slot, RadScheduler knows that the Appointment will last from x to y hour on the same day. Choosing All Day Event will reset the Start and End Hours, hence the Appointment will last zero days. RadScheduler automatically adds one day just to fix this inconsistency.
If you try the second case, and then edit the Appointment, you will see that one day has been added to the End Date, although you have entered the day before when creating the Appointment.
All the best,
Simon
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.