RadScheduler

When set, this property automatically updates the ActiveViewDefinition property to the corresponding ViewDefinitionBase object from the ViewDefinitions collection. Setting an invalid index has no effect.

The Add Appointment button executes the AddAppointmentCommand when tapped, opening the appointment creation dialog. You can style button properties like background color, text color, font, icon, border, and size.

The command can be used to customize the behavior when users click the add appointment button in the scheduler header. By default, it opens the appointment creation dialog. You can replace this with a custom ICommand implementation to provide different behavior.

This command is only applicable in agenda view and provides a way to handle agenda item double-tap events. The SchedulerNode parameter represents the specific agenda item that was double-tapped, allowing for item-specific operations.

On desktop platforms (Windows/macOS), double-tapping an agenda item automatically opens the appointment edit dialog. On mobile platforms (iOS/Android), single tap is used for dialog opening, while double-tap fires this command.

This command is only applicable in agenda view and provides a way to handle agenda item tap events. The SchedulerNode parameter represents the specific agenda item that was tapped, allowing for item-specific operations.

This command provides a way to handle appointment double-tap events programmatically. The Occurrence parameter contains information about the specific appointment instance, including the underlying IAppointment data, actual start/end times (for recurring appointments), and recurrence state.

On desktop platforms (Windows/macOS), double-tapping an appointment automatically opens the edit appointment dialog. On mobile platforms (iOS/Android), single tap is used for dialog opening, while double-tap fires this command.

The appointments source can be any collection implementing IEnumerable<Appointment>. For automatic UI updates when appointments are added/removed, use ObservableCollection<Appointment>. Each appointment must implement the IAppointment interface with properties like Start, End, Subject, etc.

You can use the following types for this collection:

• Appointment - A complete ready-to-use implementation of IAppointment with additional properties like Body, Location, UniqueId, and URL. This is the recommended type for most scenarios as it provides all necessary functionality out-of-the-box.
• IAppointment - The core interface that defines the contract for appointment objects. This interface must be implemented if creating custom appointment types. Requires implementing properties like Start, End, Subject, IsAllDay, RecurrenceRule, TimeZone, plus methods for Copy(), CopyFrom(), Equals(), and INotifyPropertyChanged support.

The AppointmentStyleSelector provides more flexibility than a single AppointmentTemplate by allowing conditional styling based on appointment properties like subject, category, importance, or custom data. The selector receives the appointment's Occurrence object and should return an appropriate Style.

This command provides a way to handle appointment tap events programmatically. The Occurrence parameter contains information about the specific appointment instance, including the underlying IAppointment data, actual start/end times (for recurring appointments), and recurrence state.

On mobile platforms (iOS/Android), tapping an appointment also automatically opens the appointment preview dialog. On desktop platforms (Windows/macOS), double-tap is used for dialog opening, while single tap only fires this command.

The AppointmentTemplate allows complete customization of appointment appearance, including layout, colors, fonts, and additional elements. The template's BindingContext is set to the Occurrence object, which provides access to the underlying IAppointment data and timing information. When null, appointments use the default built-in template showing the subject text.

The culture setting affects:

• Date and time formatting in headers and appointments
• First day of the week in week and month views

This property supports two-way data binding. When the user navigates to different dates using gestures or navigation buttons, this property is automatically updated.

The backward navigation button executes the DecreaseVisibleRangeCommand when tapped. The navigation decrement depends on the active view definition (1 day for day view, 1 week for week view, etc.). You can style button properties like background color, text color, font, border, and size.

This command is executed when:

• The user taps the backward navigation button
• Swipe gestures navigate backward (when InteractionMode allows)
• Programmatic navigation methods are called

You can provide a custom command to handle navigation events or add additional logic.

The header border surrounds the entire header area including navigation buttons, title, and view switcher. You can style properties like background color, border thickness, corner radius, and padding.

The header label displays formatted date information based on the active view definition and HeaderTextFormat property. For example, it might show "October 2023" in month view or "October 16-22, 2023" in week view. You can style text properties like font size, color, weight, and alignment.

The forward navigation button executes the IncreaseVisibleRangeCommand when tapped. The navigation increment depends on the active view definition (1 day for day view, 1 week for week view, etc.). You can style button properties like background color, text color, font, border, and size.

This command is executed when:

• The user taps the forward navigation button
• Swipe gestures navigate forward (when InteractionMode allows)
• Programmatic navigation methods are called

You can provide a custom command to handle navigation events or add additional logic.

Available interaction modes:

• None: Disables gesture-based navigation; users can only navigate using buttons
• Pan: Enables pan gesture navigation between time periods (swipe left/right to navigate)

When Pan mode is enabled, users can swipe horizontally to move between weeks, months, or days depending on the active view definition. This provides a more fluid navigation experience.

The Today button appears in the scheduler header and executes the TodayCommand when tapped. Hiding this button removes one navigation option but may be useful for custom UI layouts.

If the user attempts to navigate to a date later than MaxDate, the scheduler will automatically clamp the visible range to MaxDate.

If the user attempts to navigate to a date earlier than MinDate, the scheduler will automatically clamp the visible range to MinDate.

This command is only applicable in month view and provides a way to handle day cell double-tap events. The DateTime parameter represents the specific date that was double-tapped, allowing for day-specific operations.

On desktop platforms (Windows/macOS), double-tapping a day in month view automatically opens the create appointment dialog for that date. On mobile platforms (iOS/Android), single tap is used for dialog opening.

This command is only applicable in month view and provides a way to handle day cell tap events. The DateTime parameter represents the specific date that was tapped, allowing for day-specific operations.

On mobile platforms (iOS/Android), tapping a day in month view also automatically opens the create appointment dialog for that date. On desktop platforms (Windows/macOS), double-tap is used for dialog opening.

This command provides a way to handle time slot double-tap events programmatically. The Slot parameter contains the start and end times of the double-tapped slot, which can be used to create new appointments or perform other slot-related operations.

On desktop platforms (Windows/macOS), double-tapping an empty slot automatically opens the create appointment dialog. On mobile platforms (iOS/Android), single tap is used for dialog opening, while double-tap fires this command.

This command provides a way to handle time slot tap events programmatically. The Slot parameter contains the start and end times of the tapped slot, which can be used to create new appointments or perform other slot-related operations.

On mobile platforms (iOS/Android), tapping an empty slot also automatically opens the create appointment dialog. On desktop platforms (Windows/macOS), double-tap is used for dialog opening, while single tap only fires this command.

The Today button executes the TodayCommand when tapped, setting the CurrentDate to DateTime.Today. The button is only visible when the IsTodayButtonVisible property is true (default). You can style button properties like background color, text color, font, border, and size.

This command is executed when:

• The user taps the Today button (if visible)
• Programmatic navigation to today is requested

The command updates the CurrentDate property to DateTime.Today and refreshes the view accordingly.

The ViewDefinitions collection supports various view types:

• DayViewDefinition - Shows a single day with detailed hourly time slots for precise appointment scheduling
• WeekViewDefinition - Displays a complete week (7 days) with configurable first day of week and weekend visibility
• MonthViewDefinition - Provides a traditional monthly calendar view with 42-day grid layout
• MultidayViewDefinition - Shows a custom number of consecutive days (2-10) in timeline format
• AgendaViewDefinition - Presents the appointments in a vertically scrolling, chronological list grouped by month, week, and day.

Users can switch between view definitions using the header controls or programmatically via the ActiveViewDefinitionIndex property. Each view definition can have its own title and formatting options.

The create appointment dialog provides fields for entering appointment details like subject, description, recurrence pattern, and other properties. The dialog's appearance can be customized using the EditAppointmentDialogStyle property.

When the user saves the appointment, it should be added to the AppointmentsSource collection to appear in the scheduler. The dialog behavior may vary slightly between platforms (mobile vs desktop).

The delete appointment dialog provides confirmation before deletion and handles different scenarios:

• For single appointments: Shows a simple delete confirmation
• For recurring appointments: May offer options to delete just this occurrence or the entire series

The dialog's appearance can be customized using the DeleteAppointmentChoiceDialogStyle and DeleteRecurrenceChoiceDialogStyle properties for different dialog types.

When the user confirms deletion, the appointment should be removed from the AppointmentsSource collection. The dialog behavior may vary between platforms, with desktop platforms showing more detailed confirmation options.

The edit appointment dialog is pre-populated with the current appointment data and allows modification of properties like subject, description, time, recurrence pattern, and other details.

For recurring appointments, the dialog may present options to edit just this occurrence or the entire series. The dialog's appearance can be customized using the EditAppointmentDialogStyle property.

When the user saves changes, the underlying appointment object in the AppointmentsSource collection should be updated. The dialog behavior may vary slightly between platforms (mobile vs desktop).

If the scheduler is not yet loaded when this method is called, the scroll operation will be deferred until loading completes. The scroll operation is animated by default to provide smooth user experience.

If the scheduler is not yet loaded when this method is called, the scroll operation will be deferred until loading completes. The scroll operation is animated by default to provide smooth user experience.

This method only applies to views that display time slots (DayView, WeekView, MultidayView) and has no effect in MonthView. If the scheduler is not yet loaded when this method is called, the scroll operation will be deferred until loading completes. The scroll operation is animated by default to provide smooth user experience.

This event is raised in conjunction with the AgendaItemDoubleTapCommand. The event args contain a TappedEventArgs<SchedulerNode> with the SchedulerNode object representing the double-tapped agenda item. This event only applies to Agenda view and is not raised in Day, Week, Month, or Multiday views.

This event is raised in conjunction with the AgendaItemTapCommand. The event args contain a TappedEventArgs<SchedulerNode> with the SchedulerNode object representing the tapped agenda item. This event only applies to Agenda view and is not raised in Day, Week, Month, or Multiday views.

This event is raised in conjunction with the AppointmentDoubleTapCommand. The event args contain a TappedEventArgs<Occurrence> with the Occurrence object representing the double-tapped appointment instance.

Platform behavior:

• On desktop platforms (Windows/macOS): Double-tap also opens the appointment edit dialog
• On mobile platforms (iOS/Android): Only fires the event; single tap opens the dialog

The Occurrence object provides access to both the underlying IAppointment data and the specific instance information for recurring appointments.

This event is raised in conjunction with the AppointmentTapCommand. The event args contain a TappedEventArgs<Occurrence> with the Occurrence object representing the tapped appointment instance.

Platform behavior:

• On mobile platforms (iOS/Android): Single tap also opens the appointment preview/edit dialog
• On desktop platforms (Windows/macOS): Only fires the event; double-tap opens the dialog

The Occurrence object provides access to both the underlying IAppointment data and the specific instance information for recurring appointments.

This event is raised before any of the built-in scheduler dialogs are closed, including:

• Create appointment dialog
• Edit appointment dialog
• Delete confirmation dialogs
• Recurrence editing dialogs

The event args provide information about the dialog type. This is useful for implementing custom save logic or validation before the dialog closes.

This event is raised before any of the built-in scheduler dialogs are displayed, including:

• Create appointment dialog
• Edit appointment dialog
• Delete confirmation dialogs
• Recurrence editing dialogs

The event args provide information about the dialog type and allow cancellation of the dialog opening. This is useful for implementing custom dialogs or modifying dialog behavior based on application logic.

This event is raised in conjunction with the MonthDayDoubleTapCommand. The event args contain a TappedEventArgs<DateTime> with the DateTime representing the double-tapped date.

Platform behavior:

• On desktop platforms (Windows/macOS): Double-tap also opens the create appointment dialog for that date
• On mobile platforms (iOS/Android): Only fires the event; single tap opens the dialog

This event only applies to Month view and is not raised in Day, Week, or Multiday views.

This event is raised in conjunction with the MonthDayTapCommand. The event args contain a TappedEventArgs<DateTime> with the DateTime representing the tapped date.

Platform behavior:

• On mobile platforms (iOS/Android): Single tap also opens the create appointment dialog for that date
• On desktop platforms (Windows/macOS): Only fires the event; double-tap opens the dialog

This event only applies to Month view and is not raised in Day, Week, or Multiday views.

This event is raised in conjunction with the SlotDoubleTapCommand. The event args contain a TappedEventArgs<Slot> with the Slot object representing the double-tapped time slot's date and time range.

Platform behavior:

• On desktop platforms (Windows/macOS): Double-tap also opens the create appointment dialog
• On mobile platforms (iOS/Android): Only fires the event; single tap opens the dialog

This event only applies to views with time slots (Day, Week, Multiday) and not to Month view.

This event is raised in conjunction with the SlotTapCommand. The event args contain a TappedEventArgs<Slot> with the Slot object representing the tapped time slot's date and time range.

Platform behavior:

• On mobile platforms (iOS/Android): Single tap also opens the create appointment dialog
• On desktop platforms (Windows/macOS): Only fires the event; double-tap opens the dialog

This event only applies to views with time slots (Day, Week, Multiday) and not to Month view.