The constraint that I mentioned in my previous post is enforced with our code because of a limitation. In case you want to, you can modify the code of the timeline and remove this constraint or modify its value so that it fits your scenario. In case you decide to build your custom DLL, I would suggest that you test your application thoroughly. Additionally, please note that we do not support custom modifications of the code of the controls.
This constraint actually leads to the result that you describe - I suppose you cannot zoom in to hours and minutes, because the time period that the timeline visualizes is big. As a result, when you try to zoom in to hours/minutes, you hit the 30 000 pixels limit and the control does not allow you to zoom in further.
Now, regarding your last question - let me explain how the timeline decides which intervals to show. Basically, it calculates the number of items it needs to create (e.g. for a 10-year-visible period, and year interval - 10 items) and the minimum number of pixels every item of the kind needs - this depends on the length of the strings representing the interval. In case none of the interval types can be displayed correctly - the strings should be fully visible, the timeBar does not create any interval items. However, once you zoom in, this condition changes to true and the timeBar creates the interval items. Once created, the interval items are not removed. However, during this process, the timeline makes sure that the width of the content does not become greater than the 30 000 pixel limit.
In this case, I would recommend that you add greater interval types to the intervals collection of the timeline or reduce the whole period that the timeline represents, so that the intervals can be displayed correctly no matter the zoom level.
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>