You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Probably no good way to get this right now. We could update the collision detector interface to also accept the active sensor in the passed context - that way you can use that to check if it is a pointer sensor and the coordinates to use.
I wonder if we should do that, or expose all of the drag drop state as the context argument instead. Any thoughts there?
I am trying to add a custom CollisionDetector that register collision when the pointer is contained within droppable container.
similar to: https://docs.dndkit.com/api-documentation/context-provider/collision-detection-algorithms#pointer-within
I am stuck with finding a way to get coordinates inside CollisionDetector function. is there a way or a workaround to get pointer coordinates inside CollisionDetector?
The text was updated successfully, but these errors were encountered: