Indeed, we fixed a couple of problems with the two-way binding of the period properties of RadTimeBar. However, I am afraid you have misinterpreted the problems that we have fixed. In case you point me to the resource, from which you found out about the fix, I will be able to provide you with additional information on the fix itself.
Currently, there is a correct order, in which the properties of the timebar should be set.
This is a result of the fact that the values are coerced against each other. In short, you need to change the order of setting properties in your code:
PeriodStart = 11/22/2011
PeriodEnd = 12/12/2011
VisiblePeriodStart = 11/24/2011
VisiblePeriodEnd = 12/10/2011
SelectionStart = 11/26/2011
SelectionEnd = 12/8/2011
I have attached my test page for your reference as well.
All the best,
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>