MantisBT - VTK
View Issue Details
0013001VTK(No Category)public2012-03-15 05:112012-03-29 15:57
Pavel Pokutnev 
David Gobbi 
highminorhave not tried
closedfixed 
 
 
TBD
incorrect functionality
0013001: BUG: False computation of min/max slice number in vtkImageSliceMapper
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.
No tags attached.
Issue History
2012-03-15 05:11Pavel PokutnevNew Issue
2012-03-15 08:26David GobbiNote Added: 0028360
2012-03-15 08:26David GobbiAssigned To => David Gobbi
2012-03-15 08:26David GobbiStatusbacklog => tabled
2012-03-15 08:26David GobbiResolutionopen => fixed
2012-03-29 15:57David GobbiNote Added: 0028405
2012-03-29 15:57David GobbiStatustabled => closed

Notes
(0028360)
David Gobbi   
2012-03-15 08:26   
Hi Pavel, thanks for reporting the bug and testing the fix.
The following commit has been created:

commit 012c45da1fe9da64f98f26014c614c03649ee163
Author: David Gobbi <david.gobbi@gmail.com>
Date: Wed Mar 14 15:08:46 2012 -0600

BUG 13001: Fix backwards compatibility of GetSliceNumberMin/Max().

In VTK 5.10 the vtkImageActor was reimplemented with vtkImageSliceMapper.
As an unwanted side-effect, the use of SetDisplayExtent caused the
GetSliceNumberMin/Max methods to always return the current slice.
This patch fixes the problem and restores backwards compatibility.

Change-Id: If01bfd47cd7bfa3d8ff98a7c8b979f628f23ec23
(0028405)
David Gobbi   
2012-03-29 15:57   
Fix was tested by reporter.
Commit: 012c45da Date: Wed Mar 14 15:08:46 2012 -0600