[Insight-users] Auxilliary/vtk

Luis Ibanez luis.ibanez@kitware.com
Thu, 02 Jan 2003 11:34:17 -0500


Hi Neil,

1) The class itk::ImageToVTKImageFilter is
    the simplest way to pass ITK images to VTK.

2) This class is a template so you don't
    need to 'build' the Auxiliary/vtk directory
    in order to use it. In fact, building the
    directory doesn't change anything with this
    class.

3) The ImageTOVTKImage and VTKImageToImage classes
    are not part of the Toolkit core. It is the
    same case for everything in the Auxiliary directory.
    All those classes are provided as 'extra' material
    that hopefuly can make your life easier when it
    comes to interface with other systems.

4) The expected way to use these two classes is to
    copy them in your project. Or if you have several
    projects linking ITK + VTK. You may want to put
    them in a separate directory (not ITK, not VTK)
    and add this directory to the list of includes
    in your CMakeLists.txt file.

Please let us know if you have further questions,


   Thanks


      Luis



----------------------------------------

Neil Killeen wrote:
> Luis et al
> 
> I am now attempting to follow the instructions in
> InsightDocuments/CourseWare/Training/GettingStarted-II.ppt
> 
> in order to write a little application that uses ITK to
> read an image and then VTK to display it.
> 
> STep 6 of this document indicates the use of an interface class
> 
> itk::itkImageToVTKImageFilter
> 
> which I find lives in
> 
> InsightToolkit-1.0.0/Auxiliary/vtk
> 
> which was not  built when I last built ITK.
> 
> 
> Question:
> 
> is using this class the one true mechanism to follow for
> interfacing with VTK ?  If so, I assume it will be built automatically
> when I turn the USE_VTK  switch on inside the ITK CMakeLists.txt file ?
> 
> As I recall (somewhat vaguely now), I ended up  (on advice) turning the
> USE_VTK  switches off, because an error in VTK was high-jacking
> the configuration process (and forced the ITK build to be installed
> under the VTK binary tree - there was no independent control of
> where the ITK install went) and because some VTK demos did
> not build.
> 
> So I don't really want to go down this path again unless I have to...
> 
> thanks
> Neil
> 
> 
> _______________________________________________
> Insight-users mailing list
> Insight-users@public.kitware.com
> http://public.kitware.com/mailman/listinfo/insight-users
> 
>