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.
NodeRenderer now uses the Node's alpha value when rendering the node in SVG, G2D and PDF outputs. It only uses this value if the new per-node opacity property is checked, so existing behaviour is preserved by default.
It's the answer to my SO question here.
The justification for this is, I have a large graph from Spark GraphX that I'd like to visualize. I render one visualization for the full graph, and then I want to render separate visualizations for subgraphs. But I want to preserve the positions of the vertices from the original graph, to maintain the visual context.
One way to do this is to set the alpha of the hidden vertices to 0 and then call the OpenORD layout with the same randomSeed as I used for the full graph visualization.