Bugzilla – Full Text Bug Listing
| Summary: | [ClassDiagram] issues with changing association class ends | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Raphael Faudou <raphael.faudou> | ||||||
| Component: | Core | Assignee: | Project Inbox <mdt-papyrus-inbox> | ||||||
| Status: | NEW --- | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | 69a2fa5b, papyrus-bugs | ||||||
| Version: | 0.8.1 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Raphael Faudou
I found my way here eventually :-) thanks for opening this bug. To add a few more details: (1) When editing an association class, IMHO most people would expect the "Delete owned end" button to remove the owned end from the association class's list of owned ends. In fact, it deletes the entire assocation class, and there doesn't seem to be a way of undoing this action. See indicated button in the attachment papyrus_ac1.png. (2) The owned end is annotated as navigable on the diagram, but is not shown in the "Navigable owned end" box. Clicking on the "+" button above the "Navigable owned end" box to try to add it, opens a browser that is rooted at the model itself, and an owned association end from elsewhere in the model can be added. (3) According to the UML metamodel, Association Class is a generalisation of both Association and Class. However, the UI for the metaproperties of Association Class that are inherited from Association is completely different to the UI for Association itself (compare with papyrus_ac2.png). This is highly confusing. Created attachment 206936 [details]
UI for Association Class
Created attachment 206937 [details]
UI for Association
|