Add support for displaying the full length of an appointment when its length is spread across multiple days.

When the RadScheduleView has a recurring appointment with no end date for its recurrence in certain scenarios multiple errors can be try/catch-ed internally, which leads to a degraded performance. One such scenario is when a recurring appointment with no end date starts before the currently displayed time period, but does not have any occurrences before the displayed time period.

As a workaround, an end date can be added to the recurrence rule of recurring appointments.

When a custom SchedulerDialogHostFactory is implemented, the recurrence choice dialog does not close when choosing whether to edit the whole series or individual occurrence and selecting OK.

Currently, the all-day area will host appointments that have their IsAllDayEvent property set to True. Additionally, we could further extend the functionality of the all-day area by providing the option to create appointments directly in it (either via double-click or via a button). 

The virtualization logic of the group headers expects equal sizes, in order to improve the performance with a lot of appointments. Currently, we do not have an option to restrict or specify a maximum size (width or height depending on the orientation of the view definition).

Currently, there is no event that tells you when the slots dragging is finished. Add an event or a method override that is called when the multiple slots selection with the mouse is finished. Consider adding an event also for the drag started.

Slots in ScheduleView with virtualization are not rendered when resetting the bound collection instead of adding one by one 

Currently, if you add an appointment that is partially in two days (lets say, start=16 Jan 2024 23:00:00; end=17 Jan 2024 13:00:00), two AppointmentItem containers are created so that the appointment continues drawing on the next day. This is the expected behavior and it brings clear visualization of the corresponding event.

In some scenarios, the user may not want to see the second AppointmentItem. For example, if the day is defined to be more than 24 hours (via the DayStart/EndTime of the DayViewDefinition). In that case, the day group may be enough to show the full appointment, so the user may not want to see the second AppointmentItem in the next day.

Add a mechanism that allows you cancel the creation of the second AppointmentItem. This could be a property that tells if the continued AppointmentItem should be created, or a method override, or a filter (like the OccurrenceFilter or AppointmentFilter).

Currently, if you define your own GroupDescriptionsSource and the last description in the collection is not DateGroupDescription, the all-day area won't be rendered. Allow the all-day area to get rendered even if the DateGroupDescription is not last in the collection.

Currently, information about the selected slots for one day can be retrieved when deriving from the SlotSelectionBehavior class or via the SelectedSlot property. We could include a way to provide information about the selected slots for more than one day.

The expand button that is used for expanding the GroupHeader is visible even when all appointments are displayed in a TimeRulerMonthViewItem.

Currently, RadScheduleView will not adjust the start and end date of the appointments depending on the time zone, in which they were created.

Allow drag and drop of an AllDayEvent from/to the AllDayArea.

Currently, you can change the size by setting the Width or Height property (based on the header's orientation) of the corresponding GroupHeader element. However, this change works only partially because of the built-in UI virtualization support. Make this work in all expected cases or introduce another API that will allow to change the size of the groups.

Currently, the groups at the left side of the view that show the days have some automatic height applied based on the current viewport. Allow setting the height of the groups manually. 

The GetOccurrencesWithoutExceptionsFromDateTimeRange should return the occurrences of a recurring appointment, without the exceptions (modified or deleted occurrences). However, now the method returns modified occurrences and skips only the deleted ones. The method should skip also the modified occurrences.  

To work this around, exclude the exceptions using their state property:

When an exception occurrence is created and the MaxOccurrences of a recurring appointment is changed, the exception occurrence is not removed.