Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 151975 - Child node view is duplicated when added to wrong compartment
Summary: Child node view is duplicated when added to wrong compartment
Status: RESOLVED WORKSFORME
Alias: None
Product: GMF-Tooling
Classification: Modeling
Component: Core (show other bugs)
Version: 1.0   Edit
Hardware: All All
: P3 normal with 1 vote (vote)
Target Milestone: 2.0   Edit
Assignee: gmf.templates-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-27 06:48 EDT by Dmitry Stadnik CLA
Modified: 2010-07-19 12:19 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry Stadnik CLA 2006-07-27 06:48:34 EDT
In TaiPan sample project:
- Add empty box to the ship A
- Move it (dnd) to the small items compartment of ship B
=> There are two empty boxes - in both compartments.

It should not be possible to move child node to wrong compartment and view 
should not duplicate.
Comment 1 Marco Mosconi CLA 2006-08-23 09:37:39 EDT
Same behaviour for me (using UML2 domain model for class diagrams).
It is possible to DnD a node in any of the existing compartments, even if there is no compartment to hold nodes of this type at all (in this case it is not duplicated). Only precondition seems to be that in the domain model there is a (containment?) reference from the EClass of the compartment-holding node to the EClass of the moved node.

The node in the wrong compartment cannot be moved anymore and when it gets deleted, an existing duplicate (in the correct compartment) is not deleted but gets corrupted.
Comment 2 Dmitry Stadnik CLA 2007-06-19 06:57:58 EDT
Not repeatable in 2.0
Comment 3 Eclipse Webmaster CLA 2010-07-19 12:19:34 EDT
[GMF Restructure] Bug 319140 : product GMF and component
Templates was the original product and component for this bug