Having done a lot of work with RadScheduler over the last couple of weeks, I have discovered that it has a serious bug in how it determines the end of day.
Conventionally, a day starts at 00:00:00 and runs through to 23:59:59. Adding one more second moves to the start of the next day.
If you are looking at the week view and you set SelectedDate to 26Dec2016 00:00:00 (I use this notation here to avoid confusion, it is of course, a DateTime value), VisibleRangeStart is correctly set to 26Dec2016 00:00:00. VisibleRangeEnd is set to 2Jan2017 00:00:00. This is wrong! VisibleRangeEnd should be 1Jan2017 23:59:59 ie the week starting 26Dec runs from 26Dec to 1Jan, NOT 2Jan !
Unfortunately, it appears that RadScheduler has been entirely coded on the principal that the day runs from 00:00:00 to 00:00:00.values which is fundamentally wrong. This causes all kinds of problems and errors proliferating when trying to do anything with the scheduler because you end up having to code to correct for the error. Drag/Drop is similarly affected.
I should clarify that visually, the scheduler appears fine, but it transacts in the background with wrong data!
Does Telerik have any plans to correct this error ?
1 Answer, 1 is accepted
The Scheduler control has worked this way since its inception, and this is an intentional design decision. This way we don't have any gaps in the scheduler timeline (for instance an event spannig a whole day is correctly calculated as a 24 hour event, which also equals its start substracted from its end, rather than the duration being 23 hours 59 minutes and 59 seconds). We don't plan to change this behavior.
Regards,
Bozhidar
Telerik by Progress