Request: ContentEdit Drag & Drop events about contenttools HOT 12 CLOSED

👍

from contenttools.

I agree these would be useful additions, happy to add. So the new events will be:

• drag
• drop (only executed if content is successfully dropped on another element that accepts the drop action)

Does that offer everything needed?

UPDATE: The drag event would receive the element dragged as a value. The drop event would receive the element dropped as well as the element being dropped onto and the placement.

from contenttools.

How about when the drop is performed in the same place?

from contenttools.

If it's dropped on the the element above, below, left, right in such a way as to stay in the same position on the page the drop event would still trigger, but it would be easy to check if it had moved by reviewing the element (if any) before it.

from contenttools.

Just updating the documentation for the additional events now - but feel free to use:

ContentEdit.Root.get().bind('drag', function (element) { ... });
ContentEdit.Root.get().bind('drop', function (element, target, placement) { ... });

from contenttools.

You're really fast! Thank you!

from contenttools.

Thank you!

from contenttools.

Oh, and the docs in the site are already updated too 👍

from contenttools.

Okay so I tried the new events. The drop event isn't getting triggered when the drag is cancelled - e.g. you drag it to the same place. I think it should still get triggered, since if you do something during the drag event, you can't perform an undo method on the drop event since it isn't called.

Maybe you can add a cancelled boolean property to the object?

I have worked around this, to capture the cancelled drag event by adding a mouseover handler to the dom element after the drag event, then removing it right after.

from contenttools.

Yeah drop only trigger if the element was dropped on another valid element, I could modify the call so that the target and placement values for the event are null if there is no valid target?

from contenttools.

@bfintal OK you should now get an event valid or invalid - hope that helps and removes the need for the workaround :)

from contenttools.

Super thanks yet again! 👍

from contenttools.