In the RadSchedulerNavigator, in the upper right corner, there is a RadDropDownList which can change he TimeZone of the RadScheduler control. Selecting new value from the dropdown part will not change the TimeZone of the control.

Incorrect conversion of the Appointment Start/End date when changing the TimeZone.

 

In this particular case, the control is bound to a custom object using SchedulerBindingSource. As demonstrated in the Binding to Business Objects help article. While using this set-up, deleting Recurrence does not delete the Exceptions collection in the business object. The exceptions collection property of the Appointment inside the RadScheduler is cleared, however, the changes are not transferred to the data object.

 

Appointments Start/End date is wrong when using different TimeZone for SystemTimeZone with DefaultTimeZone. Appointments are placed in the wrong date or the start/end properties are wrong in the EditAppointmentDialog.

AllDay event is rendered on two days when using different TimeZone for SystemTimeZone with DefaultTimeZone

The control uses DateTime.Now. The RadScheduler control can be enhanced by adding support for the TimeProvider class in its date-time calculations.

When an appointment has a very short duration (seconds-level, e.g., 1 second and 0 minutes), it does not appear in the RadPrintPreviewDialog. The appointment is visible in the scheduler UI but missing from the print preview.

For example:

Dim ap1 As New Appointment
ap1.Start = New Date(Date.Today.Year, Date.Today.Month, Date.Today.Day, 15, 0, 0)
ap1.End = New Date(Date.Today.Year, Date.Today.Month, Date.Today.Day, 15, 0, 1)
ap1.Description = "not printed"
ap1.Summary = "not printed"
RadScheduler1.Appointments.Add(ap1)