Not sure if it is any help but here is a code snippet from my own HDF5
image reader code:
outInfo->Set( vtkDataObject::ORIGIN(), DataOrigin, 3 );
outInfo->Set( vtkDataObject::SPACING(), DataSpacing, 3 );
this->DataExtent[0] = this->DataExtent[2] = this->DataExtent[4] = 0;
this->DataExtent[1] = xDim-1;
this->DataExtent[3] = yDim-1;
this->DataExtent[5] = zDim-1;
outInfo->Set( vtkStreamingDemandDrivenPipeline::WHOLE_EXTENT(),
DataExtent, 6 );
outInfo->Set( vtkStreamingDemandDrivenPipeline::UPDATE_EXTENT(),
DataExtent, 6 );
_________________________________________________________
Mike Jackson [EMAIL PROTECTED]
BlueQuartz Software www.bluequartz.net
Principal Software Engineer Dayton, Ohio
On Oct 27, 2008, at 7:55 PM, Dominik Szczerba wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
What else then WHOLE_EXTENT, UPDATE_EXTENT and SetExtent and do I have
to fill in RequestInformation/RequestData of my plugin reader (derived
from vtkImageAlgorithm) in order for Paraview to see the dataset's
extents? Only bounds are displayed in the Information tab, while for
native file formats there is also extents. But when I save the file in
legacy format for a test the extent is written correctly, so it WAS
known to Paraview, only not displayed properly. What is wrong?
- --
Dominik Szczerba, Ph.D.
Computational Physics Group
Foundation for Research
on Information Technologies in Society
http://www.itis.ethz.ch
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFJBlT0/EBMh9bUuzIRAtPEAKCCl5p8xH1lEDNGCLJcrDQyVQBKEACeKipg
7+d3ZVAZYn26NjZ9AcZyCsg=
=oV+K
-----END PGP SIGNATURE-----
_______________________________________________
ParaView mailing list
ParaView@paraview.org
http://www.paraview.org/mailman/listinfo/paraview
_______________________________________________
ParaView mailing list
ParaView@paraview.org
http://www.paraview.org/mailman/listinfo/paraview