Hi, John.
That issue (if we are indeed talking about the same issue) is cause by wrong RowHeight. For each larger skins, such as Bootstrap / MetroTouch, you must set bigger RowHeight say 30 or 35 pixels.
For the upcoming 205 Q2 release, we have tweaked our code so if you set Bootstrap skin and do not set RowHeight, the internals of RadScheduler will set the property to 30px, in terms avoiding the issue.
Do not that if you set it to a smaller value, the issue will remain.
Can you test that the issue is fixed for you if you set RowHeight to 30-35 pixels manually?
Regards,
Ivan Zhekov
Telerik
That issue (if we are indeed talking about the same issue) is cause by wrong RowHeight. For each larger skins, such as Bootstrap / MetroTouch, you must set bigger RowHeight say 30 or 35 pixels.
For the upcoming 205 Q2 release, we have tweaked our code so if you set Bootstrap skin and do not set RowHeight, the internals of RadScheduler will set the property to 30px, in terms avoiding the issue.
Do not that if you set it to a smaller value, the issue will remain.
Can you test that the issue is fixed for you if you set RowHeight to 30-35 pixels manually?
Regards,
Ivan Zhekov
Telerik
See What's Next in App Development. Register for TelerikNEXT.