Colormap opacity enabled after switch to categorical and back
On current PV master, 5/3/2023, with the new colormapping UI reorganization, there is an unexpected behavior enabling opacity mapping. To reproduce:
- load Source .. Data Objects .. HyperTreeGrid (or any dataset with something that can be a categorical color map)
- color by
vtkEdgeFlags
- show the Color Map Editor. Notice "Enable Opacity Mapping for Surfaces" is disabled
- enable "Interpret Values as Categories". Immediately disable.
- "Enable Opacity Mapping for Surfaces" is now enabled, and my surface has disappeared.
Note that if I now explicitly disable "Enable Opacity Mapping for Surfaces" at this point, it sticks - I can switch to categorical and back without a problem. Maybe this points to default value handling somehow?
I also see that when "Interpret Values as Categories" is on, an "Enable Opacity Mapping for Surfaces" option is present and enabled by default.