[vtkusers] Edges and Solids
Sean McInerney
seanm at nmr.mgh.harvard.edu
Thu Jul 29 12:02:42 EDT 2004
vtk at scil.sinp.msu.ru wrote:
> On Wed, 28 Jul 2004, Sean McInerney wrote:
>
>>> ieh.... it is dramatically slow if number of objects is over 10-20
>>> (eats 35% of CPU).
>>> I have 180-200 objects...
>>
>> As long as you do not need to select and drag the actors around as a
>> unit, you can try vtkPropAssembly. This should function similarly for
>> picking, but without the shared matrix stack evaluation done by
>> vtkAssembly. Note that vtkAbstractPicker subclasses implement a number
>> of methods that will be of use: GetProp(), GetAssemblyPath(), and
>> GetPropAssembly().
>
> Thanx!
>
>> I am assuming that you want to maintain a separate vtkProperty and/or
>> vtkTexture for each Actor. If this is not important, consider using
>> vtkAppendPolyData to combine all or similar PolyData sources for use
>> with a single Mapper and Actor.
>
> what about colors for each cell of such an (all-in-one) actor?
> or color is the property of the actor as whole?
>
The all-in-one actor could have cell scalars used with a lookup table
for coloring. As far as I know, this will only affect the front faces.
The only way to affect the back faces is via the actor's BackProperty.
-Sean
More information about the vtkusers
mailing list