-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Hide edges on viewport animation #2477
Comments
I think that the scope of the proposed feature should be expanded: An option to hide edges on any animation is not sufficient. Maybe it's sufficient for your use-case, but it could cause conflicts in others. For example, a consumer may want to animate one particular edge and hide the other edges. (1) This feature should not be coupled with (2) This feature should not be coupled to animation. One approach would be to allow for manually setting when edges should be hidden. That's more flexible, but it has usability concerns: A consumer could mistakenly use something new Generally, I'd prefer to remove features like |
Or do you mean that you want to hide edges for viewport-only animations, such as an animated pan? |
Ah yes, sorry, I was not clear in the initial post. I just meant for animated pans/zooms. |
Maybe we could just add |
Yes, unless |
|
Ref : Hide edges on viewport animation #2477
I tried the proposed change with |
Issue type
Feature request
Description of new feature
Setting
hideEdgesOnViewport
totrue
in the initialization options can give a performance improvement in very large graphs when the user pans and zooms. However, when the viewport is animated withcy.animate()
, the edges remain visible.Animating the viewport of very large graphs may be more performant if edges are hidden during the animation.
Motivation for new feature
I have a large graph (~1k nodes and ~6k edges). Visualizing it is quite performant, but animating it isn't at all.
It's possible to do a workaround: you can, before animating, update the style to set edges to
visibility: hidden
and then back tovisibility: visible
incy.animate()
's callback. However, performance here is unpredictable -- some animations just jump, others are quite smooth.I'm not familiar with this project's codebase, but if someone can confirm that this should give a perf boost in theory, then the change should be as simple as changing this line to check if the graph is animated:
The text was updated successfully, but these errors were encountered: