Hi J-P Minderhoud,
First of all, thank you for the constructive feedback and for the kind words.
Straight to your questions:
- I am not sure what you mean, and in case I misunderstood you, please explain in detail the current behavior and the expected one.
I suppose you mean that when you have RotatorType=Buttons/ButtonsOver, positioning the mouse over a rotator item while they are scrolling, does not stop the animation. This behavior is by design and in my opinion, this is the correct behavior. We would however appreciate your point of view on the matter. Do you expect the animation to stop as soon as the mouse is over a rotator item?
- The different RototorTypes have different behavior when using the showNext method - in some cases, it shows the next item and in the rest - the next viewport. For the time being, RotatorType=FromCode is of the second type. The behavior you expect in this case is possible and I will log it for consideration. In case we decide that this is what the user expects, we will change it.
- We are aware of this problem and it is on our TODO list.
- Generally, when you set the Width / Height of a control, you set the Width / Height of the control as a whole and its parts should size according to the values of these properties. These settings should not depend on any other setting of the control. In particular, in case the RadRotator was implemented the way you suggest, setting RotatorType=Buttons would cause the control to take up more space of the page, than it is specified with its Width/Height properties. And switching RotatorType to "AutomaticAdvance" would cause a change in the layout of a page, as the space the RadRotator takes would decrease. I hope you agree, that this would lead to a lot of problems when building the layout of a page.
- In general, you are correct. However, we have done this on purpose, because this would make out job on implementing the features we have on our TODO list for the RadRotator, easier. We have not yet implemented the functionality we envision for this control and that is why this behavior seems strange to you. We, for example, intend to make it possible for the developer to change the RotatorType on the client.
- Thank you for these feature requests. I have forwarded all of them to our developers and we will do our best to implement them for SP1, scheduled for the last week of August.
I have updated your Telerik points for taking the time to prepare this list of questions and feature requests.
All the best,
the Telerik team
Check out Telerik Trainer
, the state of the art learning tool for Telerik products.