Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure node searching is handled well for large trees #364

Closed
gibsramen opened this issue Sep 1, 2020 · 0 comments · Fixed by #433
Closed

Ensure node searching is handled well for large trees #364

gibsramen opened this issue Sep 1, 2020 · 0 comments · Fixed by #433

Comments

@gibsramen
Copy link
Collaborator

Came up in this morning's (09/01/2020) meeting.

When there are a lot of tips in a tree (i.e. EMP with 300k), the search box auto-suggestion can be very slow. For example if the node names are the sequences (TACGTCA...), searching for "TAC" takes a long time as there are potentially many nodes to be suggested.

@kwcantrell had the idea of maybe showing only the top N hits. Alternatively we could make the auto-suggestion functionality optional for users who are visualizing large trees.

@kwcantrell kwcantrell mentioned this issue Oct 26, 2020
@kwcantrell kwcantrell added this to the Third Beta Release milestone Oct 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants