|
|
|
|
Re: Attribute order in class diagram [message #1740815 is a reply to message #1740775] |
Thu, 18 August 2016 16:59 |
|
I save the reputation of the forum by giving an answer:
free software is not free beer.
OK
I am not aware of a method to reorder attributes or methods within a class shape in Papyrus.
Such a method would maybe an improvement. I would not classify it a bug, because neither the UML nor the SysML require such a method.
[Updated on: Thu, 18 August 2016 17:19] Report message to a moderator
|
|
|
|
|
|
Re: Attribute order in class diagram [message #1740869 is a reply to message #1740825] |
Fri, 19 August 2016 08:51 |
Tobias AnyName Messages: 5 Registered: July 2016 |
Junior Member |
|
|
Well, if there are buttons as shown in the screenshot and those buttons are to "move selected items up" and those iteams are attributes and after moving them up there is no change in the graphical representation, then I would call this a bug... as long no one in the community has an explanation for what the buttons are good for otherwise.
However, Papyrus is so advanced and even the classes arrange itself automatically. If there is no way to set the order of attributes in a class, I would be surprised. Therefore I did not file it as a bug, but as a question to the community with the hope that a pro-user is giving suggestions on how to order the attributes.
[Updated on: Fri, 19 August 2016 08:55] Report message to a moderator
|
|
|
Re: Attribute order in class diagram [message #1740873 is a reply to message #1740869] |
Fri, 19 August 2016 09:18 |
|
Hi Tobias,
I think you mix up tree representation of the model with a shape on a diagram. The buttons you mention are related to the order within tree representation of the model. These buttons change to order within the tree representation of the model and that works as intended.
The order within a shape within a diagram that illustrate an element of the model is a completely different story. Papyrus allows you to use different graphical representations of the very same element of the model in different diagrams. As an example you might omit the attribute compartment of a class shape in one diagram while presenting it in another.
It is the same story with the order of attributes within a class shape. The order may (the UML specification does not disallow it) be different on two shapes representing the very same class of the model on to different diagrams.
Regards
Carsten Pitz
PS I refined "model" by "tree representation of the model", because the model itself has no element order.
[Updated on: Fri, 19 August 2016 09:45] Report message to a moderator
|
|
|
|
Powered by
FUDForum. Page generated in 0.04737 seconds