Re: Why no display lists in Quesa?

[James W. W. <os...@jw...>]

On Jun 19, 2005, at 12:16 AM, Frank Condello wrote:

> Yes, but if someone is updating a trimesh every frame (which isn't  
> an unreasonable expectation) you'll be compiling a new display list  
> every frame, which will certainly be slower than using the current  
> vertex array path.

I suppose some might do that, but it would not be a concern in my use  
of Quesa.

> To use display lists to their potential you need a geometry type  
> that's guaranteed never to change, or some sort of flag for  
> existing geometries that allows you to declare them as "static"  
> once their data is set.

It would be easy enough to use an object property as a flag.