[vtkusers] Problem in loading big images using vtkimagereader
Michael Jackson
mike.jackson at bluequartz.net
Wed Aug 11 09:43:08 EDT 2010
there _is_ but the actual code in the vtkImageReader2 class uses the
"long" and not the "vtkIdType" which would help solve the problem. An
example is the following that was posted to the ParaView mailing list:
In the void vtkImageData::AllocateScalars(); method the following
should be used:
vtkIdType extent[6] ={ this->Extent[0], this->Extent[1], this-
>Extent[2],
this->Extent[3], this->Extent[4], this-
>Extent[5]};
instead of
const int* extent = this->Extent;
In the case of vtkImageReader2 it is probably "long" instead of int.
Either way on Windows, both are a 32 bit integer no matter how you
compile it.
___________________________________________________________
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jackson at bluequartz.net
BlueQuartz Software Dayton, Ohio
On Aug 11, 2010, at 9:35 AM, John Drescher wrote:
>> http://public.kitware.com/pipermail/paraview/2008-March/007422.html
>>
>> Is when I came across the issue. I did not keep track of what the
>> eventual
>> "fixes" were but somewhere (probably a private email) I think it
>> was said
>> that a fix was difficult because the API for a lot of filters would
>> need to
>> be changed.
>> In the most draconian fix the use of "long" should just be
>> banned, but
>> this would cause all sorts of backwards compatibility issues.
>>
>
> Isn't there an option when building VTK to use 64 bit ids? I have
> never used that so I am not sure how much of the code supports this.
>
> John
More information about the vtkusers
mailing list