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
Just noticed that there is a bug on the old website, when an elbow connector is used to point to a product (connected with an annotated MIM-conversion interaction). The product is not loaded in the Table (for substrates, this didn't seem an issue). I wanted to add the issue here, so we can take this into account for the new website development.
Visual representation of the issue:
Annotated interaction is not loading a substrate or product (3rd row in Table):
The product is connected to the interaction, through an elbow connector:
Converting the interaction to a straight line, resolved the issue in the Table:
Note: I don't believe the issue was caused, by adding the "side-metabolites" (L-serine and L-alanine) to different anchors, I connected both to one anchor (also connected to the enzyme), and that did not resolve the issue.
The text was updated successfully, but these errors were encountered:
khanspers
transferred this issue from wikipathways/wikipathways.github.io
Sep 7, 2022
Hi all,
Just noticed that there is a bug on the old website, when an elbow connector is used to point to a product (connected with an annotated MIM-conversion interaction). The product is not loaded in the Table (for substrates, this didn't seem an issue). I wanted to add the issue here, so we can take this into account for the new website development.
Visual representation of the issue:
Annotated interaction is not loading a substrate or product (3rd row in Table):
The product is connected to the interaction, through an elbow connector:
Converting the interaction to a straight line, resolved the issue in the Table:
Note: I don't believe the issue was caused, by adding the "side-metabolites" (L-serine and L-alanine) to different anchors, I connected both to one anchor (also connected to the enzyme), and that did not resolve the issue.
The text was updated successfully, but these errors were encountered: