Ability to distinguish beween types of group headers and apply fixed width to one type of group headers and force the rest of them to calculate their size automatically.
Available with the R3 2016 SP1 release.
Disscused here: http://www.telerik.com/forums/freezing-row-in-timeline-view-in-radscheduleview
Make it possible to set a range of dates in which the RadScheduleView can navigate its ViewDefinitions. Navigation in that range should be possible via the left/right buttons in the top right corner or the DatePicker control also at that location.
Currently the Appointment StartTime and EndTime are exported with TZID ( TimeZone ID) which must not be applied when the times are specified in UTC and leads to incorrect values when imported in Outlook. Available in LIB version 2016.2.530, it will be also available in the 2016 R2 SP1.
When set the ActiveViewDefinitionIndex to more than 0, the event triggers 3 times, it also depends on what is the ViewDefinition. Available in LIB version 2016.1.201, it will be also available in the 2016 SP1 Release.
This is only happening for Appointments in the future or in the past.
In EditAppointmentDialog, if the user tries to create an invalid recurrence pattern, the Ok button is not updating its state to disabled immediately ( it is updated when the dialog is moved). This also affects another scenario described below: 1. Using RadScheduleView (WPF), create an appointment with a duration of 27 hours 2. Close the Edit Appointment dialog to see the appointment created properly in the calendar. 3. Double-click the appointment you just created, to edit it. 4. Click the Edit Recurrence button 5. Change from Weekly to Daily (note that the OK button is now disabled) 6. Change the duration from 27 hours to 3 hours OK button is still disabled If I do it in the opposite order, change the duration to 3 hours and then the recurrence pattern the OK button is enabled. Available in LIB version 2015.2.817, it will be also available in the 2015 Q3 Release.
Available in LIB version 2015.2.831, it will be also available in the 2015 Q3 Release.
Clearing a bound collection to the SpecialSlotsSource property does not remove the cleared objects from the memory