@ Les: with firefox and jquery everything is already pretty fast. so difficult to say. it sure ain't slower !
I didn't do testing with a large grid or in IE6-7.
Thanks Tony.
I must admit, I overlooked this optional id you can set when creating these buttons.
(just for future reference, like this:
.jqGrid(“navButtonAdd”,”#tree_pager”,{
sorry i took some time to answer, i had to deliver the application.
In the end we decided to remove the treegrid from this applicatoin, due to performance issues: i have a tree with 2 root elements and each one has about 400-500 children. it loads quickly, but closing the folder (to hide the children) it took about 8 sec's!
Anyhow, back to the original problem:
I've tried it like this:
colNames:['level','Id','Name','Description','info'],
ah, I see.
I'm using JSON, and my data is like this:
{"total":"1","rows":[{"level":"0","isLeaf":"false","expanded":"false","description":" group description" ,"name":"groupname01","parent":"null","id":"groupname01"},{"level":"1","isLeaf":"true","expanded":"true" ,"name":"name02","parent":"groupname01","id":"name02"} ....
So the level is sent first.
I don't have “info” in my JSON, this is an extra column in the view, that I map to the name (with jsonmap:”name”) because i need that to construct the url.
So I think i have everything for option 2, or do i need to do something else? I'm not sure I understand “named conventions”, do you mean i need to explicitly define in my jsonReader to use “level”?
Thanks already,
Stefan
Tony, Thank you for the new beta.
I just did a test with jQuery 1.3.1 (tried this before, but it didn't work) and the new jqGrid 3.4beta2.
And my issue from above is solved.
Can you point me to what you changed to get this working, if it's not too much?
Thanks again,
Stefan
I'm sorry, I've should have been more clear:
I'm using your wonderfull component in a result page. I've set the rows to display to 2, and the result from the search contains 3 records, so I can show off the paging functionality.
So when displaying the first 2 rows, it works beautiful, no vertical scrollbar. when I click for the next page, I get a list with one record (the 3th). now when I click back to show me the first 2 rows again, I get the vertical scrollbar.
Any clue?
mmm, in my downlod of 3.2.1 in grid.base.js on line 1055 it's still using “collapse” ??
Is it somewhere else corrected?
Thanks
Hi tony,
This “visibility:collapse” gives me a vertical scroll bar in FF2. If I use “display:none” this works fine for me in FF2.
I'm using height:”auto” as css-height for the table.
Can you tell me why you use visibility:collapse?
Thanks,
Stefan
Copyright 2014 TriRand LtdAll Rights ReservedRSS
Back to Top