Transactions, Edges and Links do not appear to be rendering correctly in the graph view, it appears to be a logic issue concerning undirected transactions. In cases where a transaction is manually created and redefined as undirected, the graph view classifies it with other directed transactions and in some cases renders it as a directed transaction.
Steps to Reproduce
Create a graph in edge mode with two Nodes, A and B.
Add a transaction from Node A to Node B
Change the value of the attribute "directed" to False (Notice the arrow disappear form the end of the transaction).
Add a transaction from Node B to node A (Note the arrow reappear on the undirected transaction).
Select the undirected transaction (Notice the arrow disappear from the undirected transaction)
Add another transaction from Node A to Node B (notice the grouping with the undirected graph and the persistence of the arrow)
Note: similar anomalies exist with links where an undirected link that was previously directed can cause a link to express association in an incorrect direction. Select link mode after step 5 and observe a bidirectional association instead of unidirectional.
Behaviour
Expected behaviour:
Undirected transaction should be treated as a separate entity. The are one of three edge types. 2x Directed + 1x Undirected. they should not be grouped with directed edges unless being represented as a link.
Prerequisites
[ ] Put an X between the brackets on this line if you have done all of the following:
Running the latest version of Constellation
Attached the Support Package via
Help
>Support Package
Checked the FAQs: https://github.com/constellation-app/constellation/wiki/FAQ
Checked that your issue isn’t already filed: https://github.com/constellation-app/constellation/issues
Checked that there is not already a module that provides the described functionality: https://github.com/constellation-app/constellation/wiki/Catalogue-of-Repositories
Description
Transactions, Edges and Links do not appear to be rendering correctly in the graph view, it appears to be a logic issue concerning undirected transactions. In cases where a transaction is manually created and redefined as undirected, the graph view classifies it with other directed transactions and in some cases renders it as a directed transaction.
Steps to Reproduce
Create a graph in edge mode with two Nodes, A and B.
Add a transaction from Node A to Node B
Change the value of the attribute "directed" to False (Notice the arrow disappear form the end of the transaction).
Add a transaction from Node B to node A (Note the arrow reappear on the undirected transaction).
Select the undirected transaction (Notice the arrow disappear from the undirected transaction)
Add another transaction from Node A to Node B (notice the grouping with the undirected graph and the persistence of the arrow)
Note: similar anomalies exist with links where an undirected link that was previously directed can cause a link to express association in an incorrect direction. Select link mode after step 5 and observe a bidirectional association instead of unidirectional.
Behaviour
Expected behaviour:
Undirected transaction should be treated as a separate entity. The are one of three edge types. 2x Directed + 1x Undirected. they should not be grouped with directed edges unless being represented as a link.
Additional Information
N/A