DragSortListView

Drag flag bit. Floating View can move in the negative x direction.

Drag flag bit. Floating View can move in the negative y direction. This is subtle. What this actually means is that the floating View can be dragged above its starting position. Remove in favor of lower-bounding item position?

Drag flag bit. Floating View can move in the positive x direction.

Drag flag bit. Floating View can move in the positive y direction. This is subtle. What this actually means is that, if enabled, the floating View can be dragged below its starting position. Remove in favor of upper-bounding item position?

Cancel a drag. Calls #stopDrag(boolean, boolean) with true as the first argument.

As opposed to getAdapter(), which returns a heavily wrapped ListAdapter (DragSortListView wraps the input ListAdapter {\emph and} ListView wraps the wrapped one).

Use this to move the check state of an item from one position to another in a drop operation. If you have a choiceMode which is not none, this method must be called when the order of items changes in an underlying adapter which does not have stable IDs (see hasStableIds()). This is because without IDs, the ListView has no way of knowing which items have moved where, and cannot update the check state accordingly.

A word of warning about a "feature" in Android that you may run into when dealing with movable list items: for an adapter that does have stable IDs, ListView will attempt to locate each item based on its ID and move the check state from the item's old position to the new position — which is all fine and good (and removes the need for calling this function), except for the half-baked approach. Apparently to save time in the naive algorithm used, ListView will only search for an ID in the close neighborhood of the old position. If the user moves an item too far (specifically, more than 20 rows away), ListView will give up and just force the item to be unchecked. So if there is a reasonable chance that the user will move items more than 20 rows away from the original position, you may wish to use an adapter with unstable IDs and call this method manually instead.

Move an item, bypassing the drag-sort process. Simply calls through to drop(int, int).

Use this when an item has been deleted, to move the check state of all following items up one step. If you have a choiceMode which is not none, this method must be called when the order of items changes in an underlying adapter which does not have stable IDs (see hasStableIds()). This is because without IDs, the ListView has no way of knowing which items have moved where, and cannot update the check state accordingly. See also further comments on moveCheckState(int, int).

Removes an item from the list and animates the removal.

For each DragSortListView Listener interface implemented by adapter, this method calls the appropriate set*Listener method with adapter as the argument.

Allows for easy toggling between a DragSortListView and a regular old ListView. If enabled, items are draggable, where the drag init mode determines how items are lifted (see setDragInitMode(int)). If disabled, items cannot be dragged.

Completely custom scroll speed profile. Default increases linearly with position and is constant in time. Create your own by implementing DragSortListView.DragScrollProfile.

Set the width of each drag scroll region by specifying a fraction of the ListView height.

Set the width of each drag scroll region by specifying a fraction of the ListView height.

This better reorder your ListAdapter! DragSortListView does not do this for you; doesn't make sense to. Make sure notifyDataSetChanged() or something like it is called in your implementation. Furthermore, if you have a choiceMode other than none and the ListAdapter does not return true for hasStableIds(), you will need to call moveCheckState(int, int) to move the check boxes along with the list items.

Usually called from a FloatViewManager. The float alpha will be reset to the xml-defined value every time a drag is stopped.

Set maximum drag scroll speed in positions/second. Only applies if using default ScrollSpeedProfile.

Probably a no-brainer, but make sure that your remove listener calls notifyDataSetChanged() or something like it. When an item removal occurs, DragSortListView relies on a redraw of all the items to recover invisible views and such. Strictly speaking, if you remove something, your dataset has changed...

Start a drag of item at position using the registered FloatViewManager. Calls through to startDrag(int, View, int, int, int) after obtaining the floating View from the FloatViewManager.

Start a drag of item at position without using a FloatViewManager.

Stop a drag in progress. Pass true if you would like to remove the dragged item from the list.