Bug 433362 - D&D tool that does not remove dragged element from source container should not delete and recreate the same DDiagramElement
Summary: D&D tool that does not remove dragged element from source container should no...
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Diagram (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2014-04-24 04:03 EDT by Steve Monnier CLA
Modified: 2014-04-28 03:50 EDT (History)
1 user (show)

See Also:


Attachments
Reproduction sample (11.39 KB, application/x-zip-compressed)
2014-04-24 04:21 EDT, Steve Monnier CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Monnier CLA 2014-04-24 04:03:44 EDT
If a drag and drop tool is used and it does not remove the element from its source container, the DDiagramElement is removed and recreated. Therefore, the user sees the same element but placed at a different position, which seems odd.
Comment 1 Steve Monnier CLA 2014-04-24 04:21:24 EDT
Created attachment 242272 [details]
Reproduction sample

The sample contain a Viewpoint Specification Project and an Ecore Project. 

The VSM provides a diagram displaying classes in their parent package. It also displays classes as list container where the list elements are the super classes. A drag and drop tool is available to update the superClasses reference.

To reproduce this issue, select C3 (as a node in the "test_ecore" package) and drop it in C1 (as a list container). The tool will update C3 superclass from C2 to C1. C3 will still be displayed as a node in the "test_ecore" package but it will be moved to a default location for new elements. It should be located where it was before Drag and Drop.
Comment 2 Pierre-Charles David CLA 2014-04-28 03:50:30 EDT
Reclassifying this as an enhancement. While the use case is interesting and we want to support it, it is out of scope of the original intent of the DnD tool. The tool was designed assuming the implementations in concrete VSMs would correspond to an actual drag'n'drop.