[Uml-devel] bug 54573 and association roles

[Oliver Kellogg]

Hi,

I tracked down bug 54573 to a problem with the irregular
role assignments not being accounted for by the association
line sorting code in AssociationWidget::updateAssociations().

What I mean by "irregular role assignments":
For generalizations, umbrello uses

	B --> A

so B is the specialized class and A is the general class.
However, for other associations (such as dependencies),
umbrello uses

	A --> B

I wonder why that is so - is it dictated by the UML standard?
I guess I'm not the only one who gets confused by this -
the author of AssociationWidget::updateAssociations() most
certainly did too :)

So my question is, shall I make a global change to umbrello
to use just one convention, i.e.

	A --> B,

or shall I just add special-casing code to updateAssociations()
to keep the different conventions apart?

Thanks,
Oliver