feat(datasource/graphene) added ability to choose a mesh bounding box #800
Conversation
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
… for graphene layer that requests a filtered manifest and additionally culls the mesh in the shader for a pixel perfect boundary
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
with a boundary requests a filtered manifest and additionally culls the mesh in the shader for a pixel perfect boundary
The currently implementation has some rough edges, before I try to refine those, we want to know your thoughts on making this a general feature, could be applied to neuroglancers root/layer/sublayer that sources could implement where given a boundary, they can further restrict what data is requested and displayed.