GitLab

- remove ComponentBlendMode from vtkVolumeMapper
- move IndependentComponents from vtkVolumeMapper to vtkVolumeProperty

1) Fixed ray casting for rendering a large image
2) Removed RGBTexture input from the volume mapper
3) Modified vtkVolumeProperty to support properties per "field"
   with a maximum of 4 fields.
4) Remove all RGBTexture parameters from the property
5) Small fix to interactor style joystick camera for endpan and endzoom

Most of this work is in preparation for multiple component support
for volume rendering in VTK.

1.) vtkTypeRevisionMacro is now used in all VTK classes in place of
    vtkTypeMacro.  It invokes the original vtkTypeMacro and then adds
    a protected CollectRevisions method for future use in serialization.
    A corresponding vtkCxxRevisionMacro has been added to every .cxx file
    to implement the CollectRevisions method for each class.  This will
    allow collection of every class revision at run time.  Any new VTK class
    should use vtkTypeRevisionMacro instead of vtkTypeMacro.  The .cxx
    implementation should then have the following line:
      vtkCxxRevisionMacro(vtkFoo, "$Revision: 1.1 $");
    CVS should insert the correct revision number when the class is commited.

2.) vtkTypeMacro now also adds a typedef called "Superclass" to refer to
    the superclass of any VTK class.  All PrintSelf methods have been
    updated to call their superclass's PrintSelf like this:
      this->Superclass::PrintSelf(os,indent);
    This should reduce the number of places that refer to a superclass
    by its actual name.

3.) The standard ::New() method implementation has been replaced with a
    macro.  Instead of an explicitly written implementation to try the
    object factory and then call the new operator, VTK classes should
    instead use the following macro unless they have a special New() method:
      vtkStandardNewMacro(vtkFoo);
    This will implement the New() method in the standard way.  The line
    should appear in the .cxx implementation file, not in the header.
    Using the macro will make it easier to change the standard
    implementation of the method.

Also removed tabs from many files.

changed cropping region planes from voxel coordinates to volume (including origin and spacing) coordinates

ENH: All unimplemented copy constructors and assignment operators made private so that errors will show up at compile time instead of link time.  Since they are not implemented, they can never be called, so they should be private instead of protected.

methods for traversing the data have been collasped into 1. Functionality has
been added for saving textures, but as this is not working perfectly yet it
has been disabled in this checkin. Second, the ray caster was obsoleted. It
has not been in use for the past week, but now all the methods have legacy
warnings and do nothing. Third, the view rays have been obsoleted - legacy
warnings on all the methods. Other changes: otherPrint.tcl - removed the
puts statement indicating what was being tested.

A new CVS repository was created on 2001-04-26 to fork VTK during
transition to a new source tree layout.  The new repository was created
using server-side symlinks referencing files in the original repository
to preserve per-file history.  This commit was manufactured during
conversion from CVS to represent the fork as a branch.

8 bit volumes. Fixed by querying the mapper for scale and bias, and using this
when creating the array in volume.

     overriding ALL versions of an overloaded function.  These were addressed
     by filling in the rest of the API.  In some cases, a subclass was
     overriding and overloading a function (changing input parameter to a
     more specific type).  For these cases, we "hid" the original function
     in the private section of the subclass.  There was one internal API
     change.  SetInput/Output(i, vtkDataObject*) was changed to SetNthInput/Output(.)

process to look at the makefile to determine abstract/concrete (rather
than requiring a "non //BTX //ETX method" to be pure virtual.

to get Java to compile. This is a bad solution, but the only one I know
of at the moment.

the definition of the gradient opacity transfer function in the volume
property to be in actual magnitude values rather than values with the
scale / bias already applied. Cleaned up some header files (moved some
methods into //BTX //ETX to keep them from being wrapped, and improved
some descriptions). Removed some methods that produced warnings in the
last version. Added warnings to obsolete methods in this version.

(vtkDataSetMapper, vtkPolyDataMapper, and vtkVolumeMapper). This way we won't
be overriding / hiding methods from the superclass anymore. As a result,
vtkMapper has gained a method called GetDataSetInput() which returns the
first input as a data set. Anything that used to call mapper->GetInput() now
calls mapper->GetDataSetInput(). vtkDataSetMapper has a GetInput() method that
returns a vtkDataSet * and vtkPolyData still has a GetInput() method that
returns a vtkPolyData *. One of the bounds methods needed to move down from
vtkAbstractMapper3D into vtkMapper and vtkVolumeMapper because it needed to
know about the input - vtkAbstractMapper3D should not require that input
for all subclasses be a vtkDataSet or that there is only one of them.

for the fact that additional info is being computed and passed to
props doing ray casting so that the right z value can be returned.

clipping planes can also be used from volume rendering. Modified the 2D texture
mapper to take advantage of this. Also, modified due to name change - since
ClippingPlanes clashed with a variable already in vtkVolumeMapper, ClippingPlanes
was renamed to CroppingBounds.