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
Think of the "multiple containers + handle" example. I need to know when the element currently being dragged is over another container (i.e. when the ghost element is shown in that container) so I can add a class to it and style it differently.
You could emit an event (and or add a class) when it moves over it and moves out (but you'd have to add the logic to figure that out). You could alternatively emit an event when the element is being dragged (i.e. it would be emitted a lot of times for one drag) and leave it up to the user to do the rest in the callback (although they might implement it inefficiently).
The text was updated successfully, but these errors were encountered:
For me, no I don't think so. But maybe someone might have their own use case that means they need more control, I don't know. I think you'd need at least some kind of drag event anyway because people might want to handle when an element is dragged over an arbitrary element (which isn't in a container) like a huge "delete" button or something.
Think of the "multiple containers + handle" example. I need to know when the element currently being dragged is over another container (i.e. when the ghost element is shown in that container) so I can add a class to it and style it differently.
You could emit an event (and or add a class) when it moves over it and moves out (but you'd have to add the logic to figure that out). You could alternatively emit an event when the element is being dragged (i.e. it would be emitted a lot of times for one drag) and leave it up to the user to do the rest in the callback (although they might implement it inefficiently).
The text was updated successfully, but these errors were encountered: