MantisBT - ParaView
View Issue Details
0003773ParaView(No Category)public2006-09-15 12:322007-03-12 16:01
Clinton Stimpson 
Berk Geveci 
normalminoralways
closedfixed 
 
 
0003773: querying opengl extensions causes a window to popup and go away
When running some pqClientClipUndo or maybe other tests, I notice a flash of a window coming and disappearing. Turns out that it comes from vtkPVOpenGLExtensionsInformation::CopyFromObject, which creates a render window and destroys it.

There should be a window coming up like that. Perhaps adding a hide/show to vtkRenderWindow? Set it hidden after creating it. Then when opengl extensions are queried, it won't show the window (call XMapWindow or whatever for the platform). Does there really need to be a vtkRenderWindow::Render to query extensions? Just creating the context should be enough, or maybe just associating the context with the window is enough, right?
No tags attached.
Issue History
2011-06-16 13:10Zack GalbreathCategory => (No Category)

Notes
(0005290)
Ken Moreland   
2006-10-06 11:25   
When you create a traditional OpenGL context, that is associated with a visible window. Although it may be possible to create a non-visible window context, in some implementations the feature set may be different with the pbuffers than the visible windows, so that is not a very safe way to quere extensions.

If at all possible, I recommend delaying the checking of extensions until after a window is created. Since there usually is no reason to use an extension until after a context is created, that should be possible.
(0005298)
Utkarsh Ayachit   
2006-10-07 19:44   
Assigning to Berk.
The plan is to reorganize vtkSMDataObjectDisplayProxy to not do the volume pipeline tests until Update() thus deferring all extension test to render time.