Community
Participate
Working Groups
The current drag and drop editing does not work intuitively when source and target representation of the element differ. Example: - A container C contains a list of Subnodes SN of Domainclass A. - Furthermore, a Node N exists which contains BorderedNodes BN of the same Domainclass A. When creating a Container drop tool with N as container and SN specified as mapping, this does not result in the desired ability to drag a list item onto a node, although the action is semantically correct (both elements contain other elements of corresponding types). As pointed out in [1], this works if the drop tool has *both* SN and BN specified as mappings. This is not intuitive (nor documented) and has the additional difference that now also dragging between different N nodes is enabled which might not be generally desired. [1]: https://www.eclipse.org/forums/index.php/m/1729544/#msg_1729528
Created attachment 261245 [details] Test Drag N Drop problem
Hi, Thank you for your feedback. To reproduce problem, use example joined: - Open new DiagClassAndPackage - Try to Drag N Drop E1 to p1. It works OK - Ctrl + Z to have E1 in diagram and not in p1 - Open TestDragNDropTool.odesign, remove the mapping BorderedDCP_ClassPort in the Container Drop tool (DCP_DropClass). - Try to Drag N Drop E1 to p1. Nothing KO We should can to drag n drop E1 to p1, without add the bordered mapping node in the container drop tool.
