Robert LeGood
Top achievements
Rank 1
Rank 1
Robert LeGood
asked on 20 Feb 2008, 08:30 PM
Hoping someone can help with some really odd rendering behavior. When a page with Rad Controls first load, it draws a page one way, then takes a second to render the page with the skin you've chosen, which makes everything "jump" and it looks really ridiculous.
Can someone explain why this happens and if there's a work around to it? Our users are beginning to complain about it.
Can someone explain why this happens and if there's a work around to it? Our users are beginning to complain about it.
8 Answers, 1 is accepted
0
Hi Robert,
Unfortunately, the provided information does not help us much in reproducing the error. It will be best if you can open a support ticket and send us a simple running project (incl. your custom skins, CSS, images, DB backup if needed and so on) demonstrating the problem (and step-by-step instructions on doing so). In that way we can reproduce and pinpoint the problems you're facing on our side, understand the logic of your application and provide a solution.
Greetings,
Paul
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Unfortunately, the provided information does not help us much in reproducing the error. It will be best if you can open a support ticket and send us a simple running project (incl. your custom skins, CSS, images, DB backup if needed and so on) demonstrating the problem (and step-by-step instructions on doing so). In that way we can reproduce and pinpoint the problems you're facing on our side, understand the logic of your application and provide a solution.
Greetings,
Paul
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Robert LeGood
Top achievements
Rank 1
Rank 1
answered on 25 Feb 2008, 04:04 PM
Here's the easiest way to demonstrate the behavior....
Create a page with a Script Manager and 200 RadTextBox's with the Web20 skin. Run the page. I can count to 4 between the time the page first draws and the time that the controls get skinned. In addition, all the text boxes are disabled until they get skinned.
I want the controls to appear skinned without that delay.
To demonstrate why it looks off, take the first RadTextBox on the page and change it's Font->Size value to XX-Large. Re-run the app and you'll notice that all the text boxes start off the same size then, when the skin gets applied the page shifts and the first text box, correctly shifts to the correct size. The more controls that have different sizing values (and the more different controls you have), the worse this gets.
Create a page with a Script Manager and 200 RadTextBox's with the Web20 skin. Run the page. I can count to 4 between the time the page first draws and the time that the controls get skinned. In addition, all the text boxes are disabled until they get skinned.
I want the controls to appear skinned without that delay.
To demonstrate why it looks off, take the first RadTextBox on the page and change it's Font->Size value to XX-Large. Re-run the app and you'll notice that all the text boxes start off the same size then, when the skin gets applied the page shifts and the first text box, correctly shifts to the correct size. The more controls that have different sizing values (and the more different controls you have), the worse this gets.
0
Robert LeGood
Top achievements
Rank 1
Rank 1
answered on 25 Feb 2008, 04:16 PM
To add a couple things...
For a comparison, create a page with 200 standard text boxes. The page renders immeidately and the controls are able to be used immediately.
If I change the first one to Font -> Size -> XX-Large, and re-run, the control is immediately larger, there is no delay as the page re-draws itself.
For a comparison, create a page with 200 standard text boxes. The page renders immeidately and the controls are able to be used immediately.
If I change the first one to Font -> Size -> XX-Large, and re-run, the control is immediately larger, there is no delay as the page re-draws itself.
0
Jason Maronge
Top achievements
Rank 1
Rank 1
answered on 26 Feb 2008, 05:06 PM
I see this also on my RadInput boxes. There is a slight delay before the skins are applied. I am assuming it takes some time to initalize the controls before the skins get applied. Not sure if anything can be done about it, but I am hoping so.
Jason
Jason
0
Hi guys,
I have tested the scenario with 200 RadTextBox controls and our latest official version of Proemetheus (Q3 sp2) but could not observe any delay in the rendering of the skins. Could you confirm this issue exists for you with that version?
Sincerely yours,
Pavel
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
I have tested the scenario with 200 RadTextBox controls and our latest official version of Proemetheus (Q3 sp2) but could not observe any delay in the rendering of the skins. Could you confirm this issue exists for you with that version?
Sincerely yours,
Pavel
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Robert LeGood
Top achievements
Rank 1
Rank 1
answered on 27 Feb 2008, 03:17 PM
Did some testing and the rendering of the skins happens right away, but the controls are still "locked" out for a number of seconds after the page loads.
With 200 RadTextBoxes, I can count to three before I can type anything into the page. Also, the "jump" still happens with any control that I alter the Font->Size property.
With 200 RadTextBoxes, I can count to three before I can type anything into the page. Also, the "jump" still happens with any control that I alter the Font->Size property.
0
Robert LeGood
Top achievements
Rank 1
Rank 1
answered on 27 Feb 2008, 04:57 PM
Here's another way to demonstrate the issue (using SP2)...
Create a page with 200 RadNumericTextBox's. Set the value to each of these controls to "3" and NumberFormat->DecimalDigits should stay at the default of "2".
Run the project and you'll note that the screen renders 200 controls with a value of "3" inside, these controls are not editable. After a 4 second delay, the controls switch to the value "3.00" (because it's set to 2 decimal places) and become editable.
I'm looking to get rid of that 4 second delay where nothing happens. It makes it look as if I've added a massive performance hit to the application and it's frustrating to users because the page loads, but the controls are not usable for a few seconds.
Thanks!
Create a page with 200 RadNumericTextBox's. Set the value to each of these controls to "3" and NumberFormat->DecimalDigits should stay at the default of "2".
Run the project and you'll note that the screen renders 200 controls with a value of "3" inside, these controls are not editable. After a 4 second delay, the controls switch to the value "3.00" (because it's set to 2 decimal places) and become editable.
I'm looking to get rid of that 4 second delay where nothing happens. It makes it look as if I've added a massive performance hit to the application and it's frustrating to users because the page loads, but the controls are not usable for a few seconds.
Thanks!
0
Hi Robert,
Indeed the behavior is observed as you described. I consulted with our developers and they agree to investigate whether improvements can be made. The scenario itself is not very trivial and because of the quantity of the controls the performance will never be without delay whatsoever.
Best regards,
Pavel
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Indeed the behavior is observed as you described. I consulted with our developers and they agree to investigate whether improvements can be made. The scenario itself is not very trivial and because of the quantity of the controls the performance will never be without delay whatsoever.
Best regards,
Pavel
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center