Community
Participate
Working Groups
Please look at the model of OMG UML 2.5.1 in this project: https://bitbucket.org/omgumlrtf/omg-uml-revision-task-force The papyrus model is in Models/UML.di There is currently only 1 diagram (StateMachine Redefinition) At the top of the diagram, there is a class RedefinableElement with 3 generalizations shown in tree layout style for 3 subclasses (Region, Vertex, Transition). Move the RedefinableElement shape horizontally towards the right of the diagram in several steps, about 1/2 of the shape width at a time, while maintaining the same relative distance between the bottom of the shape of RedefinableElement and the top of the shapes of the 3 subclasses. In principle, this should only affect the vertical segment of the generalization edges but the horizontal segment should be unaffected. In practice, something else is happening: the horizontal segments of the generalization tree edges shift towards the bottom of the diagram seemingly proportionally to how far right the RedefinableElement shape is moved.
Created attachment 265800 [details] Initial diagram
Created attachment 265801 [details] 1st move to the right
Created attachment 265802 [details] 2nd move to the right
Created attachment 265803 [details] 3rd move to the right
Created attachment 265804 [details] 4th move to the right
Created attachment 265805 [details] 5th move to the left
Created attachment 265806 [details] 6th move to the left
The horizontal segments of the generalization lines progressively move towards the bottom of the diagram for the 4 moves to the right and for the last 2 moves to the left.
The problem with tree layout still occurs in newer releasesm including the latest Papyrus v4.5. When moving elements or reopen a diagram the tree lauout is broken. Pressing F5 or the "refresh diagram" button help sometimes, and in sometimes it only result in a toogling between correct and broken layout. In mine opinion, the tree layout is unusable as it only creates frustration.
