Hi, I am wondering, why ScheduleView is so much different to Scheduler?
So I have some questions:
1) Is there a way that ScheduleView's Timeline View (which is completely different) has the same look as the Scheduler's Timeline View?
2) The Scheduler provides events, which are fired, when the View Mode is changed (ActiveViewDefinitionChanged), or when the Selected View Start Date changed (SelectedViewStartDateChanged). Where are these events in ScheduleView?
Please answer me as soon as possible.
Thanks,
Ronald
So I have some questions:
1) Is there a way that ScheduleView's Timeline View (which is completely different) has the same look as the Scheduler's Timeline View?
2) The Scheduler provides events, which are fired, when the View Mode is changed (ActiveViewDefinitionChanged), or when the Selected View Start Date changed (SelectedViewStartDateChanged). Where are these events in ScheduleView?
Please answer me as soon as possible.
Thanks,
Ronald
1 Answer, 1 is accepted
0
Hi Ronald,
Straight to the answers:
1) No. This is in our plans, but with relatively low priority, so I cannot say when we will have the ability to display the appointments in timeline as in RadScheduler. There is a slight probability to deliver this feature with Q2 2011 in the summer, but I cannot promise it at this time.
2) We have only one event VisibleRangeChanged (and a VisibleRangeChangedCommand command too, in case you want to handle the change in your viewmodel). Why do you need to handle the view definition changes? I suppose I could provide some workaround, if VisibleRangeChanged is not enough. If you are loading appointments on demand, please browse our online demos to the "Load on demand" example for more information.
Greetings,
Valeri Hristov
the Telerik team
Straight to the answers:
1) No. This is in our plans, but with relatively low priority, so I cannot say when we will have the ability to display the appointments in timeline as in RadScheduler. There is a slight probability to deliver this feature with Q2 2011 in the summer, but I cannot promise it at this time.
2) We have only one event VisibleRangeChanged (and a VisibleRangeChangedCommand command too, in case you want to handle the change in your viewmodel). Why do you need to handle the view definition changes? I suppose I could provide some workaround, if VisibleRangeChanged is not enough. If you are loading appointments on demand, please browse our online demos to the "Load on demand" example for more information.
Greetings,
Valeri Hristov
the Telerik team