OlegKI suppose you are .NET developer which use Web Forms. What you described about the user expirience can be realized not only withthe session state. The information from the session state will be permanently send to the server and returned from the server which decrease the performance. The user wants just to open the page with the same settings
OlegKHi Piotr
I think you can use the last version jqGrid 4.3.1. You can just replace all (there are two) “>option” texts to ” option”: replace '>' to blank. You can do this easy in both jquery.jqGrid.src.js and jquery.jqGrid.min.js.
@Tony: I hope you read this thread and will make the fixes in the main code of jqGrid.
Best regards
Oleg
OlegKThe HTML fragment which you posted don't contain the closing tag
OlegKYes, it's what I mean. Pobably I expressed me not clear enough before. In general one can excape or use a numerical code of any ISO 10646 character (see here) used in the selector.
You can use code like
$.extend($.jgrid, {
OlegKHello Tony,
if one uses formatoptions: { newformat: 'n/j/Y' }
OlegKHello Tony,
it's a pity that the bug still not fixed in the jqGrid. The easy way to test the problem would be define jqGrid with local data and the “Search” button in the navigator. The date from the searching dialog will be parsed with respect of formatoptions.newformat opetion of the colModel. If one would use formatter: 'date', formatoptions: { newformat: 'n/j/Y' } or formatter: 'date', formatoptions: { newformat: 'ShortDate' } the date will be wrong parsed currently.
I can extend the bug fix to include support of 'n' format and the different “name” forms like 'ShortDate', 'ISO8601Short' and so on. My current suggestion to fix the code of parseDate is the following
parseDate : function(format, date) {
OlegKYou are right. The bug exist in the two lines of code inside of $('.ui-pg-selbox',”#”+pgcnt).bind('change',function() {…}.:
if(tp) { $('.ui-pg-selbox',ts.p.pager).val(this.value); }
else if(ts.p.toppager) { $('.ui-pg-selbox',ts.p.toppager).val(this.value); }
OlegKLook at the place in the documentation. Try to use
var myUserData = $("#grid_id").getGridParam('userData');
alert(myUserData.Column1);
or try to use the as additional option userDataOnFooter: true
OlegKFirst of all you should read documentation including the list of limitations of the current implementation. It can save many time. Here you can find that grouping are not supported with frozen columns.
Best regards
Oleg
OlegKProbably you have the problem described here. I would recommend you to read the answer,
OlegKHello,
you call $.ajax inside of NIKCheck which works
OlegKHello fabamb,
I don't think that one should include in the code of jqGrid any changes which break the current server code. Your suggestion require changes on the server side because the code SELECT TOP(0) will work not good. On the other side if you use “SQL Server Management Studio” for example it uses per default TOP(1000) in all your selects of the tables. It's good because mostly you will not look through all returened rows and examine only some first rows. So I think that the usage of some large enough value like 5000 will be better. One can include the value as a new jqGrid option together with the text 'All'
OlegKSorry, but is my demo work correctly in your environment? If it works than you should debug your code and verify why the setFrozenColumns method still not executed. Probably you use some additional options of jqGrid which are not supported by frozen columns (see the limitations here)? For example you could uses scroll:1 (scroll:true) or something like that.
Best regards
Oleg
Copyright 2014 TriRand LtdAll Rights ReservedRSS
Back to Top