Items reordering in a list-based control is a pretty handy feature and it is used in various use cases. From simple scenarios like configuring settings, defining tabs order to complex scenarios like managing user content, and reordering images or email. With the recent Xamarin.Forms 5.0 release, Drag and Drop gesture recognizers were introduced and enable you to unlock these scenarios in your app. In this post I will guide you through everything you need to add drag & drop to your CollectionView.
In previous posts you may have seen how drag and drop can be used with any control with the new gesture recognizers in Xamarin.Forms. However, views inside CollectionView
organized by the control itself, are special and include caching and virtualization. These optimizations can break if you start moving views around. Don't worry those as gesture recognizers can still be used to work with the views indirectly. The recognizers have useful properties to bind them to commands with parameters:
<DragGestureRecognizer
...
DragStartingCommand="{Binding ...}"
DragStartingCommandParameter="{Binding ...}" />
<DropGestureRecognizer
...
DragOverCommand="{Binding ...}"
DragOverCommandParameter="{Binding ...}"
DragLeaveCommand="{Binding ...}"
DragLeaveCommandParameter="{Binding ...}"
DropCommand="{Binding ...}"
DropCommandParameter="{Binding ...}" />
This is enough to track user requests to move one item to some other location. The item
here is an element of a collection, bound to the CollectionView
control. And if you can change the order of the items in the underlying collection, you can do the same with the new gesture recognizers.
First, you need a view model with a collection, where you want to reorder items. The items reordering logic is defined in C# with no UI-dependent code. A basic algorithm that takes one item of a collection and moves it in front of another item of the same collection. You need a few properties in the view model and the core reordering logic:
public ICommand ItemDragged { get; }
public ICommand ItemDraggedOver { get; }
public ICommand ItemDragLeave { get; }
public ICommand ItemDropped { get; }
private async Task OnItemDropped(ItemViewModel item)
{
var itemToMove = items.First(i => i.IsBeingDragged);
var itemToInsertBefore = item;
if (itemToMove == null || itemToInsertBefore == null || itemToMove == itemToInsertBefore)
return;
var categoryToMoveFrom = GroupedItems.First(g => g.Contains(itemToMove));
categoryToMoveFrom.Remove(itemToMove);
var categoryToMoveTo = GroupedItems.First(g => g.Contains(itemToInsertBefore));
var insertAtIndex = categoryToMoveTo.IndexOf(itemToInsertBefore);
itemToMove.Category = categoryToMoveFrom.Name;
categoryToMoveTo.Insert(insertAtIndex, itemToMove);
itemToMove.IsBeingDragged = false;
itemToInsertBefore.IsBeingDraggedOver = false;
}
Next, to make it closer to a real-world example, the items in the CollectionView
are grouped by category. And the algorithm above can drag items between categories:
public class ItemViewModel : ObservableObject
{
public string Category { get; set; }
public string Title { get; set; }
private bool isBeingDragged;
public bool IsBeingDragged
{
get { return isBeingDragged; }
set { SetProperty(ref isBeingDragged, value); }
}
private bool isBeingDraggedOver;
public bool IsBeingDraggedOver
{
get { return isBeingDraggedOver; }
set { SetProperty(ref isBeingDraggedOver, value); }
}
}
Finally, you need to disable any Drag and Drop logic defined by the gestures using the Drop
event. This ensures that only the logic defined by the view model is used to reorder items:
private void DropGestureRecognizer_Drop_Collection(System.Object sender, Xamarin.Forms.DropEventArgs e)
{
e.Handled = true;
}
You can reorder items in a CollectionView
by reordering items in the underlying collection bound to the CollectionView
. The Drag and Drop gesture recognizers can help you to trigger the reordering logic, defined by a view model, that holds the collection. This solution doesn’t use any native code, the items reordering logic is defined in a view model while the gesture recognizers take advantage of the MVVM to communicate with that logic. You can also customize the look and feel for an item being dragged and a targeted area, everything in XAML with HotReload enabled. You can use this solution today with any collection-based control, taking this sample repo as a starting point.