Bug 238887 - We can drop eAttribute in the operations Compartment of an EClass
Summary: We can drop eAttribute in the operations Compartment of an EClass
Status: RESOLVED FIXED
Alias: None
Product: Ecoretools
Classification: Modeling
Component: General (show other bugs)
Version: 0.8   Edit
Hardware: PC Windows XP
: P3 normal
Target Milestone: M7   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: Ergonomy
Keywords: contributed, plan
Depends on:
Blocks:
 
Reported: 2008-06-28 14:07 EDT by Simon Bernard CLA
Modified: 2011-05-20 05:31 EDT (History)
0 users

See Also:

Attachments
patch (10.40 KB, patch)
2008-06-28 14:23 EDT, Simon Bernard CLA 		vincent.hemery: iplog+
Details | Diff
View All 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 Simon Bernard CLA 2008-06-28 14:07:15 EDT 
If you drop an EAttribute in the operations compartment of an EClass, this eAttribute is now visible in the attributes compartment and in the operations compartement.

It's the same thing for EOperation.
Comment 1 Simon Bernard CLA 2008-06-28 14:23:18 EDT 
Created attachment 106064 [details]
patch

When you drop an element, GMF checks if the "move" is possible only at Semantic level and not at notational level.

I proposed a patch with a custom CreationEditPolicy which checks if the reparent view is possible thanks to the EcoreVisualIDRegistry.

I think this policy must be generated by GMF ...
Comment 2 Jacques LESCOT CLA 2009-04-20 10:37:05 EDT 
Fixed in HEAD
Comment 3 Jacques LESCOT CLA 2009-04-20 10:37:47 EDT 
Patch applied