3.2.0

Shift multi-select with paging problem

(I have posted this same post in a previous post that other guy puts in version 2. I repost my comment in the correct place, Version 1.0)

Hello:

I have the same problem: using the paging patch provided in the download, when I try to multi-select with shift I obtain an error.

I've seen part of the problem: when I try to get the array of indexes selected, it have the correct number of components, but they have an erroneous offset.

for example: I have 35 elements, in 4 pages, 10 element each and 5 the fourth. If I select the first 20 elements (Click in the first row, go to the next page, and shift-click in the last row), the index values starts in the first index of the last page: {30,31,32,33,34,35,36...} up to the twenty values.

Obviously when I acces to the java-script array of data to retrieve my fields, it crash in the index 36, because it never exist.

I can do a workaround, obviously, when this error happens, substracting the total of the pages-1 * PageSize to all the values, but it is a little buggy for me.

I don't know if this is a strange belhaviour because I haven't configure somethig OK, or if it's a bug.

Thanks in advance.
Mithur
December 12,
I think this is not a bug, because each page is a diferent object ( well same obj containing diferent rows set), so you can not make any selected-rows-refference to a "previous" (or next) page populated.
I would sugest to try with a second grid (without "document.write(...)" command, that include all rows , or "pagingless") to keep (retain) the selections you do on the paged one (but it's just a tought, I never tryed it).
Carlos
December 12,

This topic is archived.

See also:


Back to support forum