Greetings,
I am using the RadScheduleView (2014.2.617.45) with the TimeLineViewDefinition. I created a button that allows the user to increase and decrease the MinAppointmentHeight during runtime. This is done through a binding to a double property on the corresponding viewmodel. By clicking the button, the property is increased/decreased by a constant value. The binding uses Mode="Default" so that the appointments will initially be scaled according to the size of the ResourceGroupHeaders.
Our problem is that once the user changes the MinAppointmentHeight for the first time, the ScheduleView seems unable to render correctly. You can see the difference in the attached screenshots. Image 1 shows the scheduler before any changes to the MinAppointmentHeight, while Image 2 shows the invalid rendering. Somehow, this only happens after the first change to MinAppointmentHeight. Every following change will cause the scheduler to render correctly again.
Could you please evaluate if this is indeed a bug? If so, would you be so kind to see if you could find any reasonable workaround until it is fixed?
Kind regards,
Hendrik
I am using the RadScheduleView (2014.2.617.45) with the TimeLineViewDefinition. I created a button that allows the user to increase and decrease the MinAppointmentHeight during runtime. This is done through a binding to a double property on the corresponding viewmodel. By clicking the button, the property is increased/decreased by a constant value. The binding uses Mode="Default" so that the appointments will initially be scaled according to the size of the ResourceGroupHeaders.
Our problem is that once the user changes the MinAppointmentHeight for the first time, the ScheduleView seems unable to render correctly. You can see the difference in the attached screenshots. Image 1 shows the scheduler before any changes to the MinAppointmentHeight, while Image 2 shows the invalid rendering. Somehow, this only happens after the first change to MinAppointmentHeight. Every following change will cause the scheduler to render correctly again.
Could you please evaluate if this is indeed a bug? If so, would you be so kind to see if you could find any reasonable workaround until it is fixed?
Kind regards,
Hendrik
3 Answers, 1 is accepted
0
Hello Hendrik,
I have tried to reproduce the described issue in a simpler project, but to no avail. I have attached it to this thread, so could you please download it and give it a try? What is different in your case?
Regards,
Yana
Telerik
I have tried to reproduce the described issue in a simpler project, but to no avail. I have attached it to this thread, so could you please download it and give it a try? What is different in your case?
Regards,
Yana
Telerik
Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos and start improving your app based on facts, not hunches.
0
Hendrik
Top achievements
Rank 1
Rank 1
answered on 14 Jan 2015, 02:31 PM
Hello Yana,
I wasn't able to reproduce the behavior outside of our application. Luckily, the error disappeared but I couldn't find the reason for that. Still, thanks a lot for your time and effort :)
Regards,
Hendrik
I wasn't able to reproduce the behavior outside of our application. Luckily, the error disappeared but I couldn't find the reason for that. Still, thanks a lot for your time and effort :)
Regards,
Hendrik
0
Hello ,
We are glad that the issue has been resolved. Do not hesitate to contact us in case of any other questions or concerns.
Regards,
Kalin
Telerik
We are glad that the issue has been resolved. Do not hesitate to contact us in case of any other questions or concerns.
Regards,
Kalin
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.