What exactly is the purpose of this, or how were you thinking this would be done?
One thing you could do, is listen for keydown and keyup in the window, then when you detect ctrl+c, you copy the selected event (which you grab in the change event of the scheduler, when a user clicks on an event, the change event fires and that event will be available in the change event) by cloning it into a new event. Then, have the user click some new time slot, and when you detect ctrl+v, add that 'copied' event to the dataSource, sync the dataSource, and refresh the scheduler (or triggering your create method would probably be better).
0
Ivan Danchev
Telerik team
answered on 11 Oct 2017, 02:54 PM
Hi Jason,
The approach Tyler described is a possible way for copying ("cloning") events in the Scheduler. I'll post several links to the API, which could be helpful. You can get the currently selected event with the Scheduler's select event. The DataSource's has add and sync methods. An event can be added through the Scheduler's API with the addEvent and saveEvent methods. The Scheduler can be refreshed with its view method: scheduler.view(scheduler.view().name)