Bit of a long shot, but is there any way of improving the performance when scrolling through larger documents?
I may be totally wrong, but I'd hazard a guess that the only parts of the document that are loaded and rendered are those that are in the View Port, and any scrolling results in the bits off screen having to be drawn. This would help memory useage, but explain the slight jerkiness in scrolling. Evidentally a compromise is to render a page or two either side.
I may be totally wrong, but I'd hazard a guess that the only parts of the document that are loaded and rendered are those that are in the View Port, and any scrolling results in the bits off screen having to be drawn. This would help memory useage, but explain the slight jerkiness in scrolling. Evidentally a compromise is to render a page or two either side.
1 Answer, 1 is accepted
0
Hi Charles,
Currently there is no way to partially pre-load the document. As you correctly guessed, only items in the view port are loaded but expanding it will only decrease the performance of scrolling since more UI elements will be shown.
If you observe the performance issues only with specific documents and/or component configurations, you can send us sample document or project so that we can examine the problem.
All the best,
Martin
the Telerik team
Currently there is no way to partially pre-load the document. As you correctly guessed, only items in the view port are loaded but expanding it will only decrease the performance of scrolling since more UI elements will be shown.
If you observe the performance issues only with specific documents and/or component configurations, you can send us sample document or project so that we can examine the problem.
All the best,
Martin
the Telerik team
Sharpen your .NET Ninja skills! Attend Q1 webinar week and get a chance to win a license! Book your seat now >>