Martin Pengelly-Phillips

Yeah, technically it makes sense (the drag has ended), but there are cases where it would be useful to defer clearing the transforms until after `onDragEnd`. E.g. #28 There's a...

> EDIT: doesn't seem like onDragMove runs at all in my case... am I missing something? Hmmm. I think that is a bug in solid-dnd (likely a regression caused by...

Fixed #33 in [0.6.1](https://github.com/thisbeyond/solid-dnd/releases/tag/0.6.1) @Bluskript . Regarding the x,y position in `onDragEnd` enhancement. I'll have a think about the best way to go there, but happy to hear ideas too.

Nice. 1. Not sure without seeing more of the context. Are you sure you are dropping on a droppable? 2. Yeah, can do that. I almost included them in the...

After extensive investigation, I decided that altering behaviour to defer clearing of the transform made code overly complicated and expectations inconsistent. For #28 I'm going to pursue a standalone auto-animate...

I've made progress on this in a refactor I'm pursuing. Essentially the overlay will be able to track its own layout and transform independently of the source draggable. I'm just...

Thanks! Interesting. The dnd state will be the authority for collision detection (using the layout and transform of the overlay). So I would expect your solution to not work as...

This is now fixed in [0.7.0](https://github.com/thisbeyond/solid-dnd/releases/tag/0.7.0) with `DragOverlay` being used for collision detection. In addition: * `DragOverlay` is auto-centered on the `Draggable` on drag start. * You can specify custom...

I'm working on a native solution to this, but got waylaid by illness for a few weeks. I'm back on it now so hopefully will have something to share soon....

For reference, this was the previous 'vertical' algorithm: ```ts const sortedTransform = (): Transform => { const delta = noopTransform(); const resolvedInitialIndex = initialIndex(); const resolvedCurrentIndex = currentIndex(); if (...