[vtkusers] Very slow mapper!?!?

[Will Schroeder]

Do not use vtkDataSetReader to view images. This is the slowest path 
possible (it treats pixels as polygons). Typically you'd want to use the 
texture mapping approach similar to that found in 
Examples/Medical/Cxx/Medical3.cxx.

Will

At 04:19 PM 7/14/2003 +0100, oliveira at alumni.deec.uc.pt wrote:
>Hi all,
>I'm using the next code to read, mapping with a lookuptable and view the
>result.
>Ok, this code work perfectly but it needs very much time to appears the
>image, and when it appears the interaction is very, very slow (for example
>to make zoom).
>I'm using a PIII (1.2) with 512M ram (win 2000 pro).
>This program also takes 96M ram when running!?!?!?
>The input image as only 64k !!!!!
>
>Is there any way to do what I want or am I using this classes in a wrong
>way?
>I think the problem is in the mapper because when I use only imageviewer
>without colormapping is very fast! Am I using the right mapper?


William J. Schroeder, Ph.D.
Kitware, Inc.
469 Clifton Corporate Parkway
Clifton Park, NY 12065
will.schroeder at kitware.com
1-518-371-3971 x102 (phone)
1-518-371-3971 (fax)