Improvements when selecting and highlighting Loops

[Auriga2]

Description

1. Selection > Select Loops highlights the Loops slightly, which is hardly visible in a larger graph. It is nice if we can highlight a bit more width, similar to transactions.

2. Individual transactions and nodes can be highlighted by selecting them across using the mouse. Individual Loops can only be selected by clicking on them.

3. Selecting a Node with a loop highlights the loop as well. Feels like it should leave the loop, similar to other transactions linked to the node.

Steps to Reproduce

As above

Expected behaviour: As above

Actual behaviour: As above

Reproduces how often: 100%

[cygnus-x-1]

Part of the issue here is that loops are rendered using an image (just like icons), whereas they should be rendered just like regular transactions. This means they need a separate set of rules specific to loops.

[github-actions[bot]]

This issue is stale because it has been open for 6 months with no activity. Consider reviewing and taking an action on this issue.

[github-actions[bot]]

This issue is stale because it has been open for 6 months with no activity. Consider reviewing and taking an action on this issue.

[github-actions[bot]]

This issue is stale because it has been open for 6 months with no activity. Consider reviewing and taking an action on this issue.

[github-actions[bot]]

This issue is stale because it has been open for 6 months with no activity. Consider reviewing and taking an action on this issue.

[github-actions[bot]]

This issue is stale because it has been open for 6 months with no activity. Consider reviewing and taking an action on this issue.

[github-actions[bot]]

This issue is stale because it has been open for 6 months with no activity. Consider reviewing and taking an action on this issue.

[capricornunicorn123]

Also for consideration in a refactor of loop rendering:

Looped Transaction Count Looped transactions express their count in a label that hovers over the center of the node.

• Link Mode - Transaction count is expressed as the total looped transactions. (Reasonable Behavior)
• Edge Mode – Directed Transaction Count and Undirected Transaction Count are layered directly over each other. (Unreasonable Behavior – better displayed side by side.)
• Transaction Mode – Transaction Count is simply expressed at 1.0 regardless of transaction count - I believe this is layering a new label of 1.0 for each looped transaction. (Unreasonable Behavior – better displayed as edge counts side by side or as single link count.)

Looped Transaction Display Looped transactions are expressed as images and follow similar color and grouping thresholds as linear transactions.

• Transaction Mode – When additional directed and undirected looped transactions are added, the color of the expressed transaction is that of the last transaction to be made. (Unreasonable behavior – Instead of expressing the most recent color why not default to edge mode.)
• Transaction Mode – Adding directed looped transactions to a node that already contains more than one undirected transaction causes the undirected transaction to change color for each new directed transaction based on the colors of the undirected transaction on that node. (Unreasonable behavior)

[github-actions[bot]]

This issue is stale because it has been open for 6 months with no activity. Consider reviewing and taking an action on this issue.