OlegKAfter you restarted the web server I could see on another computer that jqGrid was automatically refreshed from the version 4.2 to 4.3 without clearing the browser cache. So the problem is solved. I think, that nobody will have the problem more.
Best regards
Oleg
OlegKHello Tony,
the both new features: frozen columns and inlane navigator begin working if the browser cache will be deleted. Probably one should force the reload the data from the wed server?
Best regards
Oleg
OlegKYes of course. I use Google Chrome 15.0.874.121 under Windows 7 64-bit.
Regards
Oleg
OlegKI want only add that the new navigator buttons will not be added in the navigator bar in Chome.
Best regards
Oleg
OlegKHello Tony,
Look at the new demo in Chrome. You will see that the columns are not frozen. Instead of than even the 'rn' column with the row numbers will be scrolled. I don't analysed the code of frozen columns so can not yet suggest the corresponding bug fix.
Best regards
Oleg
OlegKHello Tony,
The next problem in the context menu that it returns always false from the contextmenu event (see here). I suggest to make the following small modification in the code
$(this).bind('contextmenu', function(e) {
OlegKHello Kevin,
I am not sure what you wait from me. I shown you that you can improve performance in you would use data parameter instead of addRowData. Your original example used the column chooser in not correct way (complare its look of your example with my and verivy includes CSS and JavaScripts.)
The problem is you have very exotical requirements so you should solve some problems yourself. The pertofmance in my modified example is in my opinion good enough. Paging work under 1 sec on my computer. If I increase the number of rows from 300 to 3000 with the same number of columns (see here) the grid still make sorting and paging under 1 sec on my computer.
If you would implement server side paging and sorting you can have much more better performance. So I don't really see any hard performance problem. Mostly I see the problem in visibility. With speaking abstractly with common grid having 200 column I can't give you any other advices.
In one my real project which I implemented for one my customer I used jqGrid with about 35 column. In the case the most columns was checkboxs. So I used rotated column headers (see here an example). It reduced dramatically the width of the grid and the need to scrol it. Additionaly for all pages where many columns was needed be shown I used some applicaton oriented filters. So selecting some items in mostly two dependend select elements the user can choose the view on the data which corresponds the the business case. So the number of columns was small enough. Additionally I made on the server “pre filtering”. I verified whether in some column all the rows contains unchecked values. In the case displaying of the column will gives for the user no information. So the server send to the client additionaly to the data the list of columns which don't need be displayed and the client code hides there on the client side.
All above are examples which one can do in the real situation. So you should analyse your problem and find the corresponding way for the situation which you has.
Best regards
Oleg
OlegKHello,
I ocationally find your question because I don't subscribed the topic: one has on the stackoverflow more better notification system as here.
Abou your question I don't full understand your problem. How I can see from the fist look at the source code the documatation is correct and beforeCheckValues will be really called with 3 parameters. So if you don't receive the 3-d parameter you should post the code which you use. On the other side I don't understand why the 3-d parameter can be interesting bacause you can define separate parameters for Add and for Edit forms (see prmEdit and prmAdd parameters of navGrid).
Best regards
Oleg
OlegKOlegKNo, look at the documentation. In the Type column you will see array only for the column which can define settings for the grouping by multiple columns. Other options like groupCollapse, groupDataSorted for example can't be set on different values for different grouping columns. Such properties are not arrays.
Regards
Oleg
OlegKHello kazi,
you should use
OlegKHello Frisco,
you should change
OlegKHello Pete,
You posted link to my old code from the answer
Copyright 2014 TriRand LtdAll Rights ReservedRSS
Back to Top