I've already answered your bug report regarding the same issue and here is my answer:
We have investigated deeply the problem you experience.
And our investigation concludes that the behavior is expected.
What happens there is:
- 1 page lifecycle (initial load of the page) in which the Scheduler is initialized and timeslots are created;
- response is sent to the client side;
- at the client side the view is changed;
- page lifecycle is triggered and executed in which:
- the Scheduler is initialized and timeslots are created (the first execution of TimeSlotCreated handlers);
- the post data coming from the client side is evaluated, viewstate is applied and the view is changed, which triggers reinitialization of the selected view;
- with the new view, new timeslots are created (the second execution of TimeSlotCreated handlers).
As you probably, see by now, this is like having a control in the aspx which is binded to a DataSource, and on PageLoad event binded to another (or even the same) DataSource - DataBound event will be fired twice.
You will have to consider the possibility of running the handler for 2 (or more) different sets of timeslots (1 for each view that is selected).
If you are experiencing difficulties in implementing this, please, feel free to contact us again - we will be happy to help you. If this will be the case, please, share a bit more details on what exactly do you need to execute on the TimeSlotCreated server event.
the Telerik team
Register for the Q2 2011 What's New Webinar Week. Mark your calendar for the week starting July 18th and book your seat for a walk through of all the exciting stuff we will ship with the new release!