Bug 519506 - Add role name in Connector End label for identification
Summary: Add role name in Connector End label for identification
Status: NEW
Alias: None
Product: MDT.UML2
Classification: Modeling
Component: Core (show other bugs)
Version: 5.3.0   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: UML2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2017-07-11 10:05 EDT by Benoit Maggi CLA
Modified: 2017-12-19 08:09 EST (History)
2 users (show)

See Also:


Attachments
Small model example (1.33 KB, application/octet-stream)
2017-07-11 10:05 EDT, Benoit Maggi CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Benoit Maggi CLA 2017-07-11 10:05:07 EDT
Currently it's very difficult to distinct connectorends, all connectorends are displayed like that <Connector End>.

Since ConnectorEnd isn't a named element, the idea would be to display the name of the role (ConnectableElement extends NamedElement) if available.

This is a pretty similar use case as Slot displaying defining feature name

Ps: latest version 5.3.0 isn't available in the version field
Comment 1 Benoit Maggi CLA 2017-07-11 10:05:52 EDT
Created attachment 269314 [details]
Small model example
Comment 2 Ed Willink CLA 2017-07-11 10:49:08 EDT
Problem seems to be that uml.edit.provider has inadequate genmodel customization and so

ConnectorEnd inherits its label feature as MultiplicityElement::isOrdered, rather than leaving it blank, which might pick something better as it does for Slot, or by specifying ConnectorEnd::role explicitly.

Not sure that isOrdered is a very get subset of the MultiplicityElement possibilities.

Ideally all major classes should be reviewed to ensure a better UML Model Editor rendering. ... but is any change a break to traditional legacy?

Workaround: for use within Papyrus a customized overriding UML provider could be supplied.
Comment 3 Benoit Maggi CLA 2017-07-12 05:17:20 EDT
@Ed: Yes we can override the label in Papyrus but I feel that doing that directly in UML would be better for the community.