Closed GoogleCodeExporter closed 8 years ago
In general, when working with a ResultSet as your data model (the result of
calling fetchData() on a ListGrid that has a DataSource), the only way to
create an ordering that is going to reliably survive filtering operations and
be compatible with paging is to create a field that stores the order, and keep
the dataset sorted on that order.
This is shown in the "Persistent Reorderable ListGrid" sample.
However in 3.1d, when specifically have all rows loaded (so no paging issues
will occur), ResultSet will allow a reorder. You will still need to save the
order to a field if you want this to work with paging.
You can also provide data as a RecordList via setData() and reordering is then
allowed.
Original comment by smartgwt...@gmail.com
on 21 Sep 2012 at 9:39
The issue isn't reordering. Reordering works fine when records are dragged
within the listgrid. When I try to drop a record from a separate listgrid, the
location of the drop is not obeyed.
Adding a sorting field and maintaining order there will not fix the problem.
When a record is transferred from one listgrid to the next, I won't know where
it was dropped. The drop index information (as far as I can tell) is not given
to the drop handler.
Original comment by cog...@gmail.com
on 21 Sep 2012 at 10:25
The drop index and drop position are available - getDropPosition() and
getEventRow().
Original comment by smartgwt...@gmail.com
on 21 Sep 2012 at 10:34
Ahh, that will be really helpful then. Thanks!
Original comment by cog...@gmail.com
on 21 Sep 2012 at 10:42
Original issue reported on code.google.com by
cog...@gmail.com
on 20 Sep 2012 at 9:18Attachments: