[vtk-developers] [VTK 0013001]: BUG: False computation of min/max slice number in vtkImageSliceMapper

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
====================================================================== 
http://vtk.org/Bug/view.php?id=13001 
====================================================================== 
Reported By:                Pavel Pokutnev
Assigned To:                
====================================================================== 
Project:                    VTK
Issue ID:                   13001
Category:                   (No Category)
Reproducibility:            have not tried
Severity:                   minor
Priority:                   high
Status:                     backlog
Project:                    TBD 
Type:                       incorrect functionality 
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             2012-03-15 05:11 EDT
Last Modified:              2012-03-15 05:11 EDT
====================================================================== 
Summary:                    BUG: False computation of min/max slice number in
vtkImageSliceMapper
Description: 
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.

====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2012-03-15 05:11 Pavel Pokutnev New Issue                                    
======================================================================