[vtkusers] Volume rendering data that is not vtkImageData

[Moreland, Kenneth]

I have been tasked with porting some of our unstructured volume rendering
code to VTK and am having trouble figuring out how to add classes to the
mapper/actor class hierarchies.  It seems that the vtkVolume class provides
the functionality I need in a prop/actor.  However, vtkVolume is constrained
to using a vtkVolumeMapper, which is constrained to using a vtkImageData as
its input.  This is a problem because I want to build a volume rendering
mapper that accepts a vtkUnstructuredGrid as its input.

Is there a way to use the vtkVolume class with mappers that do not render
vtkImageData, or is there a trivial change that could be made that would
allow it to?  Adding a vtkAbstractVolumeMapper between vtkAbstractMapper3D
and vtkVolumeMapper might do the trick.  Or is it really necessary to write
a separate prop class for volume rendering each of the vtkImageData,
vtkRectilinearGrid, vtkStructuredGrid, and vtkUnstructuredGrid data object
types?

-Ken

   ****      Kenneth Moreland
    ***      Sandia National Laboratories
***********  
*** *** ***  email: kmorel at sandia.gov
**  ***  **  phone: (505) 844-8919
    ***      fax:   (505) 844-9297
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 2455 bytes
Desc: not available
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20021002/eec3ab23/attachment.bin>