You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all thank you for the awesome work on interfacing dash and VTK! Coming from the Python world, I was really impressed how smoothly I could move from my usual Python vtk tools to dash_vtk (thanks for that utils module ;) )
I was wondering if there could be an easy way for users to introduce their own custom colormap presets in a Representation, something I can imagine a lot of people would want to do at some point... (No matter how many options are available, I guess there will always be THAT crucial one missing...)
Would it be possible to go beyond the provided list, or is it a limitation that comes already from vtk.js? I'm thinking of a simple syntax reflecting the presets definition like this one:
But there might be other options... I was expecting to have such an option through the mapper argument of the Representation, being used to do a mapper.setLookupTable, but I failed to find out how exactly the colormap information is passed to the mapper...
Thank you!
The text was updated successfully, but these errors were encountered:
Thanks for your kind words and we can surely support what you are suggesting. Do you want to make a PR to support either String(name) or Object(presetObj) and just skip the lookup if object here.
Hi,
First of all thank you for the awesome work on interfacing dash and VTK! Coming from the Python world, I was really impressed how smoothly I could move from my usual Python vtk tools to dash_vtk (thanks for that
utils
module ;) )I was wondering if there could be an easy way for users to introduce their own custom colormap presets in a
Representation
, something I can imagine a lot of people would want to do at some point... (No matter how many options are available, I guess there will always be THAT crucial one missing...)Would it be possible to go beyond the provided list, or is it a limitation that comes already from
vtk.js
? I'm thinking of a simple syntax reflecting the presets definition like this one:But there might be other options... I was expecting to have such an option through the
mapper
argument of theRepresentation
, being used to do amapper.setLookupTable
, but I failed to find out how exactly the colormap information is passed to the mapper...Thank you!
The text was updated successfully, but these errors were encountered: