You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"The order of objects in the SVG matters for things like clicking. If a group object is listed after all or most of the member nodes in the svg, you can't click the individual nodes because you are basically clicking the box and not the node underneath. Similarly, for elbow interactions, if they are drawn after one or more nodes, their path blocks the underlying nodes from clicks as well. The results is that in some pathways, some nodes are not clickable in the svg." (adapted from Alex's description).
This is solved by bringing all data nodes to the front in PathVisio.
Proposed feature: Add a feature to PathVisio to automatically place all nodes above in every pathway right before "save" operations. The manual steps that solve this issue are:
Open pathways in PV
Select all data nodes (Right-click, Select > Select all DataNodes)
Right-click on a node (with all nodes selected) and choose Order > Bring to front.
The text was updated successfully, but these errors were encountered:
There is a known bug with svg generation, in summary:
"The order of objects in the SVG matters for things like clicking. If a group object is listed after all or most of the member nodes in the svg, you can't click the individual nodes because you are basically clicking the box and not the node underneath. Similarly, for elbow interactions, if they are drawn after one or more nodes, their path blocks the underlying nodes from clicks as well. The results is that in some pathways, some nodes are not clickable in the svg." (adapted from Alex's description).
This is solved by bringing all data nodes to the front in PathVisio.
Proposed feature: Add a feature to PathVisio to automatically place all nodes above in every pathway right before "save" operations. The manual steps that solve this issue are:
The text was updated successfully, but these errors were encountered: