[vtk-developers] vtkOpenGLPolyDataMapper::RenderPiece

[Lisa S. Avila]

Hi Bob,

MakeCurrent must be called any time the window may have become uncurrent 
(for want of a better term!) This can happen unexpectedly - and I actually 
spent many hours on several problems tracking it down to an uncurrent window.

During the rendering process a prop may update, causing its mapper to 
update. The mapper may get data that is pulled from another window - 
causing that other window to become current. Or, a start / end method on 
some filter may have a render call into another window (as is done with the 
pipeline viewer)

If you think this is a serious issue, we can start keeping "global" state 
information in the render window. You'll still make the 120,000 calls, but 
they will simply check the current state and return if no MakeCurrent is 
actually necessary.

Lisa


At 02:55 PM 5/25/2001, obara wrote:
>Hi Folks,
>
>Doesn't vtkOpenGlRenderWindow::MakeCurrent() only have to be called once
>when rendering the window?  We were rendering a simple scene 120x's and
>found this function being called 120,000 because
>vtkOpenGLPolyDataMapper::RenderPiece() calls
>vtkOpenGlRenderWindow::MakeCurrent().
>
>At least I didn't ask anything about indentation or where to put braces.
>
>Thanks in advance,
>
>Bob
>
>Robert M. O'Bara
>Senior Software Engineer
>Simmetrix Inc.
>1223 Peoples Ave.
>Troy, NY 12180
>
>Lab: (518) 276-2867
>Main Office: (518) 276-2729
>
>
>
>_______________________________________________
>vtk-developers mailing list
>vtk-developers at public.kitware.com
>http://public.kitware.com/mailman/listinfo/vtk-developers