Forum
14:56
20/10/2009
I noticed that interface in general becomes slower (especially in IE) as more rows get preloaded – and more rows it gets the slower it becomes. Especialy noticable it is on row selection, check the demos of virtual/true scrolling, try to load more then 500 rows and click around to select them, notice the delay, then try to load even more rows, try to select again and notice the delay becoming bigger.
At first I thought it had something with my extension of jqGrid, but then I narrowed it down to setSelection() call.
22:39
20/10/2009
Interesting, just noticed that true scrolling demo actually always empties the table before preloading new rows. It's exactly the behavior I'm looking for, although I couldn't find what parameters are different from the ones I use in my installation.
From what is written in documentation:
"scroll
boolean or
integer
Creates dynamic scrolling grids. When enabled, the pager elements are disabled and we can use the vertical scrollbar to load data. When set to true the grid will always hold all the items from the start through to the latest point ever visited.
When scroll is set to value (eg 1), the grid will just hold the visible lines. This allow us to load the data at portions whitout to care about the memory leaks. Additionally this we have optional extension to the server protocol: npage (see prmNames array). If you set the npage option in prmNames, then the grid will sometimes request more than one page at a time, if not it will just perform multiple gets."
I can conclude that I should use scroll = 1, right? But that's just what I do. Hm... lost.
13:59
27/10/2010
Hi,
I do not see how this is working. On the demo when you scroll down page by page, the pages are not unloaded. When you scroll up the pages ARE unloaded.
Also on my grid, when I scroll up the pages are unloaded.
But there is need to unload pages on scroll down also, the performance degrates very fast if the pages are not unloaded.
Is there any solution for that?
Thank you in advance.
11:49
27/10/2010
Together with the other serious bug in jqgrid virtual scroll, this is a major issue. It is beyond me why nobody is replying, just to aknowledge the bug, I am not even asking for a solution right now. Or if you are sure this is not a bug why don't you just say this? Both bugs are visible in your demos!!
16:28
Moderators
30/10/2007
Hello,
Yes , this is true.
Regards
Tony
For professional UI suites for Java Script and PHP visit us at our commercial products site - guriddo.net - by the very same guys that created jqGrid.
23:06
21/06/2012
Hello
I found the reason for this bug - and by the way 2 solutions:
1. Your API's response can provide the requested page number at the same level as the "total" and "records" nodes. This node has to be named "page" or something else, if you map it in (e.g.) jsonReader.
2. Because we know which page we've requested, it's not logically and nessesary to transmit this via request and response. So you could change this line
in "jQuery.jqGrid.min.js", "jQuery.jqGrid.src.js" or "grid.base.js"
to this one
Hope that helps
I submit that to github. We'll see, if it will be merged. Tony? Still alive?
Best
Robert
Most Users Ever Online: 715
Currently Online:
53 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
OlegK: 1255
markw65: 179
kobruleht: 144
phicarre: 132
YamilBracho: 124
Renso: 118
Member Stats:
Guest Posters: 447
Members: 11373
Moderators: 2
Admins: 1
Forum Stats:
Groups: 1
Forums: 8
Topics: 10592
Posts: 31289
Newest Members:
, razia, Prankie, psky, praveen neelam, greg.valainis@pa-tech.comModerators: tony: 7721, Rumen[Trirand]: 81
Administrators: admin: 66