-
-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Add option to move Connection Layer behind Primary Layer #590
Comments
This is because connections are drawn on a different layer than nodes, and this layer is above the drawing layer of nodes. So a "Bring To Front" above connections is not possible. |
As the connection layer's position can only be set for the whole diagram I've renamed the feature request. @jbsarrodie I've just done some testing and it is possible to move the connection layer behind the primary layer so that connections are drawn behind nodes. I don't know if this is useful or even if there are side effects. What do you think? The code is in branch |
Hi. I don't really like this option because if a connection is drawn behind an element then people will understand it as two relationships (one to the element and one from the element). @VinceAxe what was the use-case? |
That's a good reason. Probably why the connection layer is in front of the primary layer by default in GEF. |
The idea behind this use case was to make a legend, in this case we have 2 times 9 Flow that are about referentials and golden data. (Might it even be a way to represent an ESB ?) |
I think the risk of misinterpretation is too strong. |
I agree, I don't think we will implement this for general usage. |
Shall we close this issue? |
On the last version of Archi (I can't remember if it was the same behavior before)
When I add a new element (even a visual note)
And I want to use "Bring to front" in order to put it over relations
It does not work and the relations stays in front of the element
![Untitled](https://user-images.githubusercontent.com/43959255/76100957-e0a3ff80-5fcd-11ea-80a9-a773e32c8830.png)
The text was updated successfully, but these errors were encountered: