BUG: False computation of min/max slice number in vtkImageSliceMapper
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
There is a compatibility issue in the new VTK 5.10.0. Due to the usage of new vtkImageSliceMapper inside of vtkImageActor, the vtkCornerAnnotation changed it behavior for "<slice_and_max>" text tag, when working with volume data. It shows always 1/1 instead of e.g 5/10 for volume data during interaction. The problem is in the wring computation of min/max slice numbers in vtkImageSliceMapper.