Introduce properties for customization of the navigation panel such as:
- Showing/hiding a today button
- Showing/hiding the selected view definition ListBox
- Showing/hiding the RadDatePicker and navigation buttons

hi,

I can I make a feature request please for the appointment item control. I'd like to be able to have the delete button hidden depending on whether my appointment wants to hide the delete button. Some appointments can be deleted, some can't. the problem with the current option of using the schedule control is that it's all appointments can be deleted or all appointments can't.

because of all the different themes and complexity around them I don't want to change the actual underlying template, so to resolve this myself I have made a source code change in AppointmentItem.OnApplyTemplate. I have added this code in to create a binding:

            // Stefan: start
            // Ensure that the can be Show and hidden depending on the appointment type
            var deleteButton = GetTemplateChild("DeleteButton") as Button;
            if (deleteButton != null)
            {
                BindingOperations.SetBinding(deleteButton, Button.VisibilityProperty, new Binding()
                {
                    Path = new PropertyPath("Appointment.ShowDeleteButton"),
                    Converter = new System.Windows.Controls.BooleanToVisibilityConverter()
                });
            }
            // Stefan: end

hopefully this can be built into the system using a multi-binding where you check for the schedule control allowing deletion and then on a per appointment basis.

Thanks,

Stefan

Make it possible to render custom elements in the TimeRuler of the control.

Possible uses could be when you want to render an indicator like the CurrentTimeIndicator but for different time zone.

This is valid for the DayView and the WorkDayView but it could be researched if applicable also for other views.

Currently, the maximum height of an appointment is determined by the MinorTickLength applied. If the slots between the ticks are too small, the appointment's subject will be clipped vertically. In Outlook there is a mechanism that applies something like a minimum height which allows the subject to be drawn regardless the actual size of the appointment.

Drag and drop is not working properly for RadScheduleView WPF running inside WindowsFormsHost, in a WPF Browser Application. When you drag an appointment, it drops it in another location. 

The hierarchy of child controls is as follows:
•	WPF XAML Browser App page, containing a WinFormsHost  (WPF)
  o	WInFormsControl containing a ElementHost control (WinForms)
   	WPFUserControl containing RadScheduleView (WPF)
Please see the attached sample project that demonstrates this issue. I would like to make the whole application WPF, however the parents of the WPFUserControl are an existing application where we want to include the RadScheduleView.

The resize (splitter) controls would be used to select (get) the time space which they wrap. For example please refer the attached screenshot.

*  SnapAppointments should cause appointments to snap to tick marks, as it does now.
 *  By default, SnapAppointments should not prevent the start/end time from falling outside the visible time range. (Or at least it should consistently prevent or allow this.)
 *  There should be another bool property that prevents/allows the start/end time to be outside the bounds of the visible time range.
http://admin.telerik.com/?Context=Support&Control=%7e%2fUserControls%2fSupport%2fThreadReply.ascx&ST=425043&SM=0

Whens scrolling a group that is Freezed to remain always in View.

When double click on the right of the ViewDefinition buttons new Appointment dialog is shown

New ViewDefinition which shows an overview of a complete year. There should be a separate Calendar for each month and the days which have appointments should appear in Bold style.

Currently it is possible to set only fixed width to the GroupHeaders.

When creating an recurrent appointment on the 31st of the month Outlook gives the user a warning: "Some months have fewer than 31 days. For these months, the occurrence will fall on the last day of the month."  And as the message indicates, the event occurrences would start on the last day of the month when the 31st does not exist. 

This will set the occurrences at the end of each month regardless of the length of the month.