Community
Participate
Working Groups
I silently fixed it on rev4857. I am now backporting this on 0.8, and checking if the bug exists on the class diagram.
The bug was that the graphical model was used to find the direction instead of using the information coming from the uml model. The use case to reproduce was a transformed diagram from Topcased. It works with diagrams created in Papyrus but a change in the uml model outside of Papyrus editor can reproduce the problem.
not reproducible on the class diagram.