ReceiveContentListener

A set of callbacks for contentReceiver modifier to get information about certain Drag-and-Drop state changes, as well as receiving the payload carrying TransferableContent.

contentReceiver's drop target behaves a little different compared to the regular dragAndDropTarget modifier. When two contentReceiver modifiers are nested on the composition tree, drop area of the parent node encapsulates drop area of the child node, meaning that they wouldn't be mutually exclusive like the regular dragAndDropTarget nesting. This becomes useful when you want to extend the drop area around a TextField by wrapping the TextField in a larger component with a contentReceiver modifier. We can guarantee that the container won't receive dragExit event when the dragging item moves over to TextField.

Let's assume we have two contentReceiver boxes named A and B where B is a child of A, aligned to bottom end.

| A | | |---| | | B |

When a dragging item moves over to A from left, then over to B, then starts moving up and goes back to A leaving B, then finally leaves them both, the following would be the list of expected ReceiveContentListener calls in order to both nodes.

• A#onStart

• B#onStart

• A#onEnter

• B#onEnter

• B#onExit

• A#onExit

• B#onEnd

• A#onEnd

The interesting part in this order of calls is that A does not receive an exit event when the item moves over to B. This is different than what would happen if you were to use dragAndDropTarget modifier because semantically contentReceiver works as a chain of nodes. If the item were to be dropped on B, its onReceive chain would also call A's onReceive with what's left from B.

Summary

open fun onDragEnd(): Unit

open fun onDragEnter(): Unit

open fun onDragExit(): Unit

open fun onDragStart(): Unit

fun onReceive(transferableContent: TransferableContent): TransferableContent?