Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 322998

Summary:	[All Diagrams] Inconsistent drop of Constraint from explorer to diagram
Product:	[Modeling] Papyrus	Reporter:	Yann Tanguy <yann.tanguy>
Component:	Core	Assignee:	Patrick Tessier <Patrick.Tessier>
Status:	ASSIGNED ---	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows Vista
Whiteboard:
Bug Depends on:
Bug Blocks:	322933, 417986

Description Yann Tanguy

2010-08-18 05:06:40 EDT

The drop policy used to allow / disable dnd of Constraint from model explorer in diagram seems inconsistent (note that I suspect this also relates to various other elements).

Currently, it is always possible to show a Constraint as a Diagram top node, even is the Constraint is not owned by (semantically) the diagram context. In addition to that, it is possible to drop the Constraint as a Child node, if the target is the Constraint owner. This behavior is inconsistent, either the constraint is expected to appear anywhere in the diagram independently from it semantic owner, or only on graphical representation of the semantic owner, but mixing these behaviors is confusing.