The timeline is resizing nicely when adding multiple TimeLineItems to the timeline (when overlapping and grouping multiple items)
But when I programatically remove these items, the timeline keeps it's height and is far to large.
Is there any way to force the timeline to refresh it's vertical size?
5 Answers, 1 is accepted
RadTimeline for Silverlight does not support the feature that you need out of the box - automatic height, based on the number of items that the control visualizes. Could you please share some additional details on your scenario - e.g. images showing current and expected result, the RadTimeline definition, etc? It would be best if you could open a new support ticket and send me a simple running project, demonstrating your setup, together with this information.
Regards,Tsvetie
Telerik
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
Rank 1
I am attaching images to show my problem.
I am using groups, and different itemtemplates, no other special setup of the timeline.
Image 1.png showing the initial state when I load the ItemsSource
Image 2.png showing how the control resizes automatically and nicely when I add more elements to the timeline.
Image 3.png showing how the control incorrectly not resizing when the elements are removed.
I hope it is a workaround for this as the control works perfect in any other way but becomes unusable for our purpose when it fills up the entire screen and never shrinks back when only few lines are required.
Rank 1
Do you have any more tips on how to fix this? Did the screenshots explain enough what the problem is?
Best Regards,
Ola
As already mentioned in my previous post, RadTimeline for Sliverlight does not support automatically calculated height, based on the number of its rows of items. That is why, I suppose you have wrapped the timeline control in a Vertical StackPanel and have not specified concrete Height. Please correct me if I am wrong. In this case, the control might behave in this manner. However, please note that this scenario is not supported. I will forward your case to our developers for consideration.
I created a simple page that demonstrates a workaround that might work for you. Please note, that as this is not a supported scenario, you need to test this workaround thoroughly in order to make sure that it indeed works for your particular case.
Tsvetie
Telerik
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
Rank 1
Thank you for this workaround, it works perfectly!! :) It seems like a simple thing to put into the control itself for a future release?
Anyhow, thanks again!
Best Regards,
Ola