I'm still having a few problems with this - it seems that it is not dataSource.read() which directly causes the crash, but the result returned from the server and passed into the scheduler through the datasource. I.e. the point at which the scheduler decides to process the result of the dataSource.read(). This distinction is important because there is always a lag between calling read() and getting the result, and during this time the user could be moving an event, which would cause the crash.
Can you think of anything I can do to mitigate this?
answered on 03 Oct 2014, 08:17 AM
In that case you could use the DataSource's requestStart and requestEnd event handlers to raise/lower a flag and based on its state - prevent the dragging by calling the e.preventDefault method in the Scheduler's moveStart event handler.
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!