[ x] I agree to follow the Code of Conduct that this project adheres to.
[ x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.
A standard double ended arrow connector does not adequately address the relationships between some entities. For example, a signal to a unit that measures temperature is different from the temperature measurement response that is returned to the inquirer. While setting up two separate arrow connectors, one out and one in, is normal it suffers from a "disconnected-ness" when moving objects.
A connector like the double line "link" connector, but with opposing arrowheads, would be an excellent change. Adding the connector "jump" ability of other connectors would be a bonus.
I have tried using "grouped" arrows, but this lacks the anchoring capabilities of standard connectors that makes connectors awesome when re-arranging graph objects. I considered a custom object, but I am not that advanced of a user and am skeptical it would have the anchoring features desired/
A standard double ended arrow connector does not adequately address the relationships between some entities. For example, a signal to a unit that measures temperature is different from the temperature measurement response that is returned to the inquirer. While setting up two separate arrow connectors, one out and one in, is normal it suffers from a "disconnected-ness" when moving objects.
A connector like the double line "link" connector, but with opposing arrowheads, would be an excellent change. Adding the connector "jump" ability of other connectors would be a bonus.
I have tried using "grouped" arrows, but this lacks the anchoring capabilities of standard connectors that makes connectors awesome when re-arranging graph objects. I considered a custom object, but I am not that advanced of a user and am skeptical it would have the anchoring features desired/