When you are using incremental mode, a different NestedSortable will be
built for each page, but they will be displayed in order, one right after
the other, causing the impression it is a single list.
When the user is sorting an item from that is between two adjacent pages in
the edge of those pages, the response won't be as smooth, and the user
might have to "move" the mouse a little bit until the element falls where
he wants.
Fixing this will involve a lot of hacking and will only be done if people
want incremental mode too much.
Original issue reported on code.google.com by berpa...@gmail.com on 15 Sep 2007 at 3:19
Original issue reported on code.google.com by
berpa...@gmail.com
on 15 Sep 2007 at 3:19