3 Answers, 1 is accepted
0
Hello Troy,
I am not sure that I understand your question - you always need to use ObservableCollection<T> as AppointmentsSource for RadScheduleView because of a bug in the Silverlight and the WPF ListCollectionView classes.
Greetings,
Valeri Hristov
the Telerik team
I am not sure that I understand your question - you always need to use ObservableCollection<T> as AppointmentsSource for RadScheduleView because of a bug in the Silverlight and the WPF ListCollectionView classes.
Greetings,
Valeri Hristov
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
0
Troy
Top achievements
Rank 1
Rank 1
answered on 26 May 2011, 04:42 PM
Well, I happen to be using a ReadOnlyObservableCollection<T> instance. The built in delete button does nothing in this scenario though.
0
In order to delete an appointment, RadScheduleView should remove it from the AppointmentsSource, hence you cannot delete appointments if you use a ReadOnlyObservableCollection<T>... The presence of the "Delete" button should be considered as a bug, though. I will see if I can fit this fix in our plans for the next week's internal build.
Kind regards,
Valeri Hristov
the Telerik team
Kind regards,
Valeri Hristov
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items