Carl A. Bauer

You should implement your DropListener such that immediately subsequent calls to `getView(position, convert, parent)` in your adapter return the correct, reordered items. Also, a call to `notifyDataSetChanged()` should be invoked...

Unfortunately, I have to disagree. Reordering should be done in the Adapter (or model, in MVC terms). I do have plans to make reordering easier by providing DragSortCursorAdapters, etc. So...

First of all, let me say that performing a time-consuming db operation on every drag-sort drop is probably not a good design strategy (considering that there exists a way to...

> I do this operate async and it don't take long time. I perform only two UPDATE SQL. It is very fast, but DSLV meantime for very short time refresh...

@tprochazka Have a look at [DragSortCursorAdapter](http://bauerca.github.com/drag-sort-listview/reference/com/mobeta/android/dslv/DragSortCursorAdapter.html) and the associated subclasses. These are in the most recent commit and should take the work out of that 2nd data-handling layer you were...

Hm. So you must be dragging while your app removes the last item or else onTouchEvent wouldn't get called. When you call notifyDataSetChanged(), it should trigger dslv to abort the...

Actually you can already animate the floating View! During a drag-sort, the floating View is drawn just as any child View is drawn; a call to `dslv.invalidate()` will redraw it....

Also check out issue #1. Specifically: https://github.com/bauerca/drag-sort-listview/issues/1#issuecomment-6596255 Let me know if that doesn't help.

What Eclipse/ADT version?

BTW, have you tried @imminent suggestion?