Connector Middle labels visibility problem

[Agecoat]

Folks,

I believe the Middle Top and Bottom labels of a connector to be at fault in certain situations.

There seems to be a behavioral difference between a connector pointing from one to another class and a connector pointing from and to the same class. I can't imagine why this should be the case. I think there should be no difference.

For a connector between classes, there is a separation between connector name and connector stereotype:

- Middle Top Label: connector name
- Middle Bottom Label: connector stereotype

For a connector pointing to itself there is no such separation:

- Middle Top Label: concatenation of connector stereotype and connector name
- Middle Bottom Label: not used (at least not for stereotype)

The problem with this is that in diagrams, you can't hide the connector stereotype while showing the connnector name. This applies to connectors pointing to itself only.

I hoped for a workaround in creating a connector between two classes and altering source and destination afterwards but the label behavior seems consistent.

Any clues how to show connector name but hide connector stereotype for connector to itself?

Thx'nAdv.

Regards,
Agecoat.
(using Corporate 8.0.858)

[Paolo F Cantoni]

Hi Agecoat,

I think I reported this about 5 years ago...  (The difference between label contents in reflexive versus non-reflexive relations).

Submit a bug report using the links below.  Maybe they lost the original report - certainly it's not on Sparx's list of imminent fixes.

Paolo

[Agecoat]

Hi Paolo,

Thanx. I did.

Five years is a long time, even if not that important. My worry, and perhaps the reason why this is not solved, is the appearant structural/conceptual base problem underneath, like no clear separation between model logic and diagram logic.

The only difference between said relation 'types' is the creation of visual appearance; the reflexive type should be implemented using a 'normal' association in the model and some script like <Ctrl-Q><Ctrl-Q><Ctrl-Q>-sequence in the diagram.

There are more problems with such a structural mixup as root cause.

But let's wait and see.

Edit: Sparx says a feature request is submitted for implementation in a future release.

Regards,
Agecoat.