jQuery Grid Plugin - jqGrid - Topic: Issues when specifying rowNum as a string in 4.5.2 http://www.trirand.com/blog/?page_id=393/bugs/issues-when-specifying-rownum-as-a-string-in-4-5-2 Simple:Press Version 5.7.5.3 tony on Issues when specifying rowNum as a string in 4.5.2 http://www.trirand.com/blog/?page_id=393/bugs/issues-when-specifying-rownum-as-a-string-in-4-5-2#p29435 Bugs http://www.trirand.com/blog/?page_id=393/bugs/issues-when-specifying-rownum-as-a-string-in-4-5-2#p29435 Hello,

Also you can then get the rowNum this way

parseInt(getGridParam('rowNum'),10);

In your previous case the returned value is always string since the select box values (rowList) are strings when they are builded in the select, not in the array.

Regards

]]> Tue, 03 Sep 2013 19:37:04 +0300 tony on Issues when specifying rowNum as a string in 4.5.2 http://www.trirand.com/blog/?page_id=393/bugs/issues-when-specifying-rownum-as-a-string-in-4-5-2#p29434 Bugs http://www.trirand.com/blog/?page_id=393/bugs/issues-when-specifying-rownum-as-a-string-in-4-5-2#p29434 Helo,

Thanks for this investigation.

As from 4.5 we make the comaparations more strong  - i.e we replace == with ===.

In your case if you set rowNum as string you should set rowList array values as string.

Regards

]]> Tue, 03 Sep 2013 19:30:41 +0300 snobo on Issues when specifying rowNum as a string in 4.5.2 http://www.trirand.com/blog/?page_id=393/bugs/issues-when-specifying-rownum-as-a-string-in-4-5-2#p29433 Bugs http://www.trirand.com/blog/?page_id=393/bugs/issues-when-specifying-rownum-as-a-string-in-4-5-2#p29433 In version 4.5.2 (don't know about other 4.5.x versions), if you specify rowNum as a string (like "100" instead of 100), the specified number of records per page (rowNum) is not selected in the rowList drop-down. The grid still governs the specified number of records correctly, but no OPTION of SELECT.ui-pg-selbox is marked as selected, which leads to confusion whenever rowNum is not equal to rowList[0]. See screenshot for demo.

Image Enlarger

I know, it would be natural to dismiss it as a non-essential problem and simply suggest specifying rowNum as an integer. However, in all my applications I remember user settings (like number of records per page, current page, etc) in cookies. So, the problem is actually caused by the fact that getGridParam('rowNum') returns a string, not the integer (so "100" instead of 100), and this is what I store in the cookies and read/apply for the grid on next page visit. Before 4.5.x, it was never a problem because rowNum could be specified with a string with no side-effects. Not anymore.

]]> Tue, 03 Sep 2013 13:23:48 +0300