| Summary: | [Class Diagram] DnD of enumeration Literals (in model Explorer) into Enumeration in diagram doesn't work | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | alanusse Mising name <agnes.lanusse> |
| Component: | Core | Assignee: | Patrick Tessier <Patrick.Tessier> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 0.7.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
alanusse Mising name
The enumeration could not be be dropped because of the code for the specific drop of an instance specification(link or node). An enumerationLiteral is also an instance specification. Now the code contains a condition to distinguish this element. The second bug about the order of order of the dropped element is due to DropTargetListener class in the common. the selection was put into a hashSet and then the hash set was visited. In this context, the order was changed. it visits by taking account the key. I have change it by using a ordered collection : arraylist in order to not lose the order of the selection Done in the revision 3293 This bug will not closed, I will only change the priority. -the job is now to code test about the literal enumeration ( creation deletion , drop etc..) in order to detect this kind of bug automatically. - another job: use this test case in order to pay attention that the order of the drop respect the order of the selection. the test about enumeration literal has been added revision 3296 done |