I think this is related to this issue: http://www.telerik.com/community/forums/preview-thread/aspnet-ajax/scheduler/radscheduler-crashes-on-dayendtime-quot-23-40-00-quot-and-minutesperrow-quot-26-quot-why.aspx and possibly caused by the fix that you guys implemented for that.
Any normal scheduler set up with:
DayStartTime 7:00
DayEndTime 11:55
TimeIncrement 45
will crash with 'this.cells.0.offsetHeight' is null or not an object
I think I've tracked down the cause of it. It happens under a very specific set of circumstances:
1) your time span (Begin time to end time) results in an odd number of time intervals
2) your end time is less than one time interval shy of midnight.
I think that Since the Radscheduler displays time intervals in pairs, it tries to pad the display out by one interval, which puts the scheduler into tomorrow, which causes the javascript to die. Setting your schedule grid end time to one interval short of midnight prevents this from happening.
Any normal scheduler set up with:
DayStartTime 7:00
DayEndTime 11:55
TimeIncrement 45
will crash with 'this.cells.0.offsetHeight' is null or not an object
I think I've tracked down the cause of it. It happens under a very specific set of circumstances:
1) your time span (Begin time to end time) results in an odd number of time intervals
2) your end time is less than one time interval shy of midnight.
I think that Since the Radscheduler displays time intervals in pairs, it tries to pad the display out by one interval, which puts the scheduler into tomorrow, which causes the javascript to die. Setting your schedule grid end time to one interval short of midnight prevents this from happening.
3 Answers, 1 is accepted
0
Hi James,
Thank you for sharing your findings in the forum. I have updated your Telerik points for the involvement.
Kind regards,
Peter
the Telerik team
Thank you for sharing your findings in the forum. I have updated your Telerik points for the involvement.
Kind regards,
Peter
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.
0
James
Top achievements
Rank 1
Rank 1
answered on 11 Oct 2012, 02:59 PM
Quick followup to this. I've discovered that anything that causes the "DayEndTime" or "WorkDayEndTime" timespan to go over 24 hours (Into tomorrow) will cause this error.
You can put a negative start time in without causing this. So if you want to span midnight, you need to start "yesterday" and go to "today" instead of starting "Today" and going to "Tomorrow"
You can put a negative start time in without causing this. So if you want to span midnight, you need to start "yesterday" and go to "today" instead of starting "Today" and going to "Tomorrow"
0
Hi James,
Thank you for sharing your findings with us. Your involvement is greatly appreciated.
Regards,
Ivana
the Telerik team
Thank you for sharing your findings with us. Your involvement is greatly appreciated.
Regards,
Ivana
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.