-
Notifications
You must be signed in to change notification settings - Fork 4
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
add way to specify custom shaders #32
Comments
Just adding the shader as text will be trivial, but I would love some assistance/feedback to add helper functions to build a collection of useful shader primitives like this one. |
would stuff like "color by component" fall under your view of primitives? any other specific examples you can think of? |
Yeah, "color by $property" is definitely one — it would be nice to have something that reads the info file and can predict/validate what values might be accessible. I'm also thinking more broadly than skeletons, since annotation layers and such also can have useful shaders. |
In this case, for example, how on earth would someone know that it's vCustom2 and not vCustom1 or... whatever? |
Skeleton shader support is now integrated into SegmentationLayerConfig objects, although smart defaults are not yet in there. |
would be nice to have a way to pass in custom shaders, e.g. for a skeleton in the segmentation layer. here's an example workaround I did just by modifying the JSON
The text was updated successfully, but these errors were encountered: