Altering Geometry

New Message Reply Date view Thread view Subject view Author view

Fernando D. Mato Mira (matomira++at++lig.di.epfl.ch)
Wed, 8 Nov 1995 17:30:04 +0100

>
application, this approach doesn't work. I am required to generate all of
the geosets, etc. for the new geometry each time a change is necessary.
>

I agree that this is a problem. Performer objects should be capable
of `piping' scalars and pointers internally.
No smarts.
Allocating, filling, deallocating, recyling, deallocating the data
should be up to the user.

For small alterations to geometry
(eg., one vertex in a whole tristrip), it would be cool if they
had a `command queue' (that's probably the way all changes should be done).

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:52:01 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.