GPU Volume Mapper does not update when the underlying volume is marked modified
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
When a volume (vtkImageData) is set as input to the GPU volume mapper, and the volume is later modified (and marked using the Modified() method), the mapper does not update itself.
The update happens only when the color transfer function set to the volume is marked modified.
Other mappers (like vtkFixedPointVolumeRayCastMapper) do not exhibit this behaviour.
This bug is also present in the 5.10 branch. A sample application is attached.
Run the sample application, and press 'l' to trigger the expected functionality. In the event handler, the image's scalars are modified (set to a constant value of 1000). If you press 'Ctrl+l', the color transfer function is marked modified.
Expected behaviour from the sample application: Pressing 'l' should turn the volume black. The behaviour I get: The volume stays white.