[vtk-developers] LookupTable madness

[David Gobbi]

On Tue, 22 May 2001, John Biddiscombe wrote:

> I'm deeply unhappy that the mapper's keep changing the scalar range of the
> lookup table/ Suppose I run some simulations and have 3 datasets containing
> field strengths. I generate a lookuptable and set the range up, then I have
> 3 actors with 3 mappers and I have to set the scalar range of all 3 to
> match my lookup table. Otherwise they take matters into their own hands and
> change them. I like to share lookuptables amongst actors so that I can plot
> field strength over different ranges and just change one set of parameters
> - having to edit all 3 mapper is tedious....
>
> Can we add a flag either to the mapper or the lookuptable which say. &*^&*
> off and stop changing my range?
> Something like
> SetMapperToUseLookupTableRange(int...)
> or
> SetLookupTableAsMaster (dodgy name, but it's my first go.)

This change belongs in the Mapper, I think.  I hardly ever use
lookup tables with mappers (mainly just with images & textures)
so I'll leave this change for someone else.  I agree that the
mapper shouldn't be messing around with the user-supplied
lookup table.

 - David