Hello!
I have a grid with virtual XMLloadondemand. When the client scrolls the time until the start of the refresh is about twice as long as the refresh itself. Can I change this time?
regards, Philipp
Ahh, now I understand the question..
When you use virtual scrolling and move the scroll button and then release the mouse button, it fires an immediate request for data (no delay). If however, you continue to hold the scroll button there is a timed delay before the data is refreshed (VirtualScrollDelay). This is done to keep you from unintentionally crashing your server by making too many unnecessary requests for data as the client 'finds' the appropriate scroll point in the grid. Just be sure not to set this value too low, or you may flood your server with unintential requests for data.
-Tony
I found the solution, it's the JS-function "VirtualScrollDelay"!
Regards, Philipp
You'll have to be more specific as to what you deem the "start of the refresh". Are you referring to when the actual HttpRequest is opened, or when the HttpResponse is received? When letting the WebGrid do databinding for you, it can only be as efficient as the datasource it is bound to. If for instance, you're binding to a datareader or a dataset, the grid must iterate through all of the data just to get the few rows that it actually needs. This is obviously a bottleneck for loadondemand f you have a large dataset. The ObjectDataSource provides a mechanism for paging or partial databinding, and the WebGrid does as well. By enabling partial databinding, you can drastically improve your page performance.
I've posted some information on how to enable partial databinding in another thread which should be helpful. http://forums.labs.infragistics.com/forums/p/668/9957.aspx#9957