Conversation
Collaborator
|
Hi Thanks for submitting this. Could you share an example video and/or code of the issue you were experiencing and that this PR solves? Thanks |
Author
|
Hi @guzmanvig — sure! Recording below. It's from a side-by-side demo of published Load time is marginally faster from the PR, but the difference is most noticeable while scrolling. Same mechanism speeds them both up. Screen.Recording.2026-09-19.at.12.20.59.PM.mov |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Displaying long proteins is slow because each visible row processes the entire protein sequence, including residues it never draws.
This limits non-wrapping translations to the residues in the current row and reuses their click-target IDs when redrawing. A row showing 40 residues from a 600-residue protein now processes 40 instead of 600.