Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322998 - [All Diagrams] Inconsistent drop of Constraint from explorer to diagram
Summary: [All Diagrams] Inconsistent drop of Constraint from explorer to diagram
Status: ASSIGNED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Patrick Tessier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 322933 417986
  Show dependency tree
 
Reported: 2010-08-18 05:06 EDT by Yann Tanguy CLA
Modified: 2015-06-26 15:27 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yann Tanguy CLA 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.