Hi, As the rotator works today, it does not only move contents according to the ScrollDirection property. It also sorts records according to ScrollDirection. Example: if i populate the rotator with records from a database with an SQL statement like "SELECT * FROM mytable ORDER BY DateSubmitted ASC", and then set ScrollDirection to "Down", the rotator starts sorting records in descending order, even though the SQL statement spcifically says to sort ascending. This is stupid in my opinion. The ScrollDirection property should do only precisely what it´s name suggests: move rotator contents in the direction set in the ScrollDirection property. The data source should decide in which order records are sorted. If I should change ScrollDirection for some reason, I will have to change the SQL statement to make records sort in the order I want them to as things are now. If I populate the rotator from code-behind, this means I will have also have to recompile the application instead of just changing the ScrollDirection property.
At present only Coverflow and Carousel modes are animated. This method should animate all rotator modes.
It will be possible to specify an ItemTemplate for RadRotator that loads its items on demand.
It would be nice to give Rotator the ability to refresh contents every x minutes or seconds right out of the box, providing a refresh interval option. This could only work when using webservices, page methods or any other data fetching method, as long as it existed :) This feature is very useful when data needs to be refresh without user intervention.
I don't ever use the radrotator because of how dated it is....sets a fixed with (rrClipRegion), rotated items flow behind that, jquery based animation...etc etc. Can we please knock this out of the park and make something like http://dimsemenov.com/plugins/royal-slider/ Look, if you guys didn't use your own rotator on the new telerik.com....something needs fixing, no? #Dogfooding
Currently the RadRotator is not displayed under mobile Chrome for iOS. The issue could be worked around by switching Chrome to "request desktop site" mode from the browser menu.