Shaun Peet
Top achievements
Rank 2
Rank 2
Shaun Peet
asked on 19 Aug 2008, 07:22 PM
When scrolling up or down, if the total height of all the items in the rotator is less than the height of the rotator itself, then the items are rendered from the bottom-up. Example:
http://huronperthlakers.ca/domains/c4thstars.ca/arenadisplay/
This is a little confusing; IMO it should be from the top-down. In addition, if the total height of the items is less than the height of the rotator then there probably shouldn't be any scrolling at all since everything is being displayed.
In a matter related to that particular page, are the client-side resizing functions going to be available with Q2 2008 SP1? Thanks,
Shaun.
http://huronperthlakers.ca/domains/c4thstars.ca/arenadisplay/
This is a little confusing; IMO it should be from the top-down. In addition, if the total height of the items is less than the height of the rotator then there probably shouldn't be any scrolling at all since everything is being displayed.
In a matter related to that particular page, are the client-side resizing functions going to be available with Q2 2008 SP1? Thanks,
Shaun.
3 Answers, 1 is accepted
0
Hello Shaun,
The behavior is expected - with the current logic, if the height of all items is smaller than the height of the rotator itself, when all items are displayed, RadRotator will take the first item and show it in the position from which the rotation is set to start - in your case the bottom. In general, the idea is to provide seamless rotation of the items and in scenario like yours we would recommend to either increase the number of items (or their height) or to set the height of the rotator to a lower value.
As for the client-side resizing, this feature is implemented in our internal builds and will be available with SP1 next week.
Regards,
Georgi Tunev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
The behavior is expected - with the current logic, if the height of all items is smaller than the height of the rotator itself, when all items are displayed, RadRotator will take the first item and show it in the position from which the rotation is set to start - in your case the bottom. In general, the idea is to provide seamless rotation of the items and in scenario like yours we would recommend to either increase the number of items (or their height) or to set the height of the rotator to a lower value.
As for the client-side resizing, this feature is implemented in our internal builds and will be available with SP1 next week.
Regards,
Georgi Tunev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Shaun Peet
Top achievements
Rank 2
Rank 2
answered on 21 Aug 2008, 02:22 PM
Hi Georgi,
Thanks for the response. The page that I demonstrated was built for a very specific purpose. It's essentially a read-only kiosk screen that grabs live scheduling information from the client's website for the purposes of showing what's going on to the people who enter their hockey arena. So, from day to day the number of things scheduled will change and I, as a programmer, will have no control of the number of items returned to the rotator for any given day.
As another FYI, the rotator completely bombs whenever there or no items at all, so I have to handle this situation as well by changing the RotatorType to "FromCode" if there are no items (seems to be the only thing that works).
I do think you ought to re-consider the logic though. If the rotator's height is 100px and there are 4 items 20px high, then all items should be shown (from the top-down) and no rotating should be happening at all. To me, the primary reason for using a rotator isn't to make the page look pretty because things are moving. The primary reason is because I have a dearth of information that needs to be displayed and not enough real estate to do so. In most cases, if I don't *have* to use a rotator, I won't. Therefore, if there is enough room to display all the information then the rotator has no reason to rotate. If this needs to be a property (RotateWithPartialData = "False") then so be it.
Please do stay true to your mantra that you've followed all along in making the life of a developer an easier one. Please do not make me try to calculate the height of the items in the page load, and then determine whether to render static content or a rotating div.
I will also open a support ticket requesting the latest build. My client wants to go live with their "kiosk" this weekend and although the current one is *ok*, with client-side resizing I can really make it look very good. I thank you for your understanding.
Shaun.
Thanks for the response. The page that I demonstrated was built for a very specific purpose. It's essentially a read-only kiosk screen that grabs live scheduling information from the client's website for the purposes of showing what's going on to the people who enter their hockey arena. So, from day to day the number of things scheduled will change and I, as a programmer, will have no control of the number of items returned to the rotator for any given day.
As another FYI, the rotator completely bombs whenever there or no items at all, so I have to handle this situation as well by changing the RotatorType to "FromCode" if there are no items (seems to be the only thing that works).
I do think you ought to re-consider the logic though. If the rotator's height is 100px and there are 4 items 20px high, then all items should be shown (from the top-down) and no rotating should be happening at all. To me, the primary reason for using a rotator isn't to make the page look pretty because things are moving. The primary reason is because I have a dearth of information that needs to be displayed and not enough real estate to do so. In most cases, if I don't *have* to use a rotator, I won't. Therefore, if there is enough room to display all the information then the rotator has no reason to rotate. If this needs to be a property (RotateWithPartialData = "False") then so be it.
Please do stay true to your mantra that you've followed all along in making the life of a developer an easier one. Please do not make me try to calculate the height of the items in the page load, and then determine whether to render static content or a rotating div.
I will also open a support ticket requesting the latest build. My client wants to go live with their "kiosk" this weekend and although the current one is *ok*, with client-side resizing I can really make it look very good. I thank you for your understanding.
Shaun.
0
Accepted
Hi Shaun Peet,
Thank you for your feedback.
The problem with RadRotator when there are no items is fixed in our internal build and we will do our best to provide you with the requested functionality (no rotation if there are not enough items) for the official Service Pack 1 as well.
Sincerely yours,
Georgi Tunev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Thank you for your feedback.
The problem with RadRotator when there are no items is fixed in our internal build and we will do our best to provide you with the requested functionality (no rotation if there are not enough items) for the official Service Pack 1 as well.
Sincerely yours,
Georgi Tunev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.