As by now I often got severe performance problems that are not solvable I now want to ask right at the beginning! I am using the RadTimeBar and I want to display one year (or sometimes a bit more) of data. This data for the x-axis looks like this:
...
01.01.2012 14:00:00
01.01.2012 15:00:00
01.02.2012 12:00:00
01.02.2012 14:00:00
01.03.2012 10:00:00
01.03.2012 20:00:00
01.03.2012 21:00:00
...
I now want to bind this data to the TimeBar and want to allow the user to drill down to the interval of hours. So that if a day is visible the user will see x bars of data - for each hour present in the data. Unfortunately I now have some problems (DateTime Values without the hour value everything is working quite well)
1) Really slow and bad performance
2) After a DateChanged event the browser even crashes (due to point one)
3) Although hour data is provided and using <telerik:HourInterval />, the smallest intervall stays on a daily basis
I would be glad to hear any information about these problems. What is the maximum amount of data for this control? Are there any performance tweaks to be done? Should this kind of functionality implemented in a different way??? Please help telerik!
Thanks a lot!!!
All the best,
Tim.
1 Answer, 1 is accepted
RadTimeBar is a content control and not an items control and it has no control over the content that you place in it. I am not sure which control you are using to show your data, but from the provided information, I suppose you should optimize the content control and not the timebar itself. You can easily check this, by removing the content control and testing the timeBar on its own with the same settings - e.g. PeriodStart, PeriodEnd, Intervals collection, etc.
One thing that you should keep in mind, is that RadTimeBar does not virtualize its content - that is, all elements of the content control are created, even the ones that are not currently visible.
Regarding your last question, about drilling down to HourInterval - due to a limitation in Silverlight framework, we have enforced a constraint for zoom-in to maximum of 30 000 pixels. Depending on the period range that the timebar shows, the minimum interval that can be displayed, might be different from the minimum interval that you have added in the Intervals collection. In your case the period range of your timebar is large and when you try to zoom in to a smaller interval, you hit the 30 000 pixel limit.
Tsvetie
the Telerik team