Here is the link to the example in the XAML SDK Repository: https://github.com/telerik/xaml-sdk/tree/master/ScheduleView/Database
Create Category and TimeMarker group descriptions that allow grouping by Category and TimeMarker.
With the current implementation fires constantly while dragging over the ScheduleView. Available in the R1 2017 SP1 Release.
When you have appointments with different heights in the horizontal view and you set the MinAppointmentHeight on the ScheduleView to the minimun appointments height, appointments with bigger heights are set to the minimum one.
Available in LIB version 2016.2.525, it will be also available in the 2016 R2 SP1 release.
In the current version of the control when DayStartTime/DayEndTime properties are set to the DayViewDefinition the DayStartTime applies only for the first day of the VisibleDays range and the DayEndTime for the last day. Available in the 2016 Q1 release: DayStartTime/DayEndTime properties are applied for each day in TimelineView.
Implement a way to strech the CurrentTimeIndicator via the whole RadScheduleView area. Available in the 2016 R2 release.
Available in the 2016 R2 release.
Example scenario: in the current implementation of the RadScheduleView when touch and drag over an appointment the scrolling action is triggered. The target of this implementation is to change the behavior so when doing the same actions you should drag the appointment.
When we implement the override CanResize method, it would be interesting to change the cursor if the CanResize method return false. Actually if the method return false, the cursor remain a resize cursor but it not reflecting the reality. Available in the 2016 Q1 Release: Added ResizeCursor property of the AppointmentItem and ScheduleViewDragDropBehavior in order to be able to change the resize cursor initially as well as during the resize operation).
As a <role> I want <ability> so that <benefit>.
your demo and then trying to download source code in the form of a solution so that I can walk through it in debug mode. So far I have failed. With 100+ controls to review in 30 days, I find this incredibly annoying and have to wonder if this will be a recurring issue if I decide to buy any of your products.
This should be per appointment logic. Currently this scenario can be achieved by customizing the default Appointment ControlTemplate. The exact approach is explained in the following article from the help documentation: http://www.telerik.com/help/silverlight/radscheduleview-howto-remove-delete-button.html A sample project can be found in our XAML SDK repository: https://github.com/telerik/xaml-sdk/tree/master/ScheduleView/RemoveDeleteButton