[vtk-developers] recent Solution: Bug in SetRenderWindow(NULL) => still a bug?

[Charl P. Botha]

On Wed, 2003-12-10 at 01:28, dean.inglis at camris.ca wrote:
> ERROR: In c:\Builder\Sources\VTK\Rendering\vtkWin32OpenGLRenderWindow.cxx, line 129
> vtkWin32OpenGLRenderWindow (01A9F02C): wglMakeCurrent failed in Clean(), error: 6
> 
> Debug: In c:\Builder\Sources\VTK\Rendering\vtkWin32OpenGLRenderWindow.cxx, line 76
> vtkWin32OpenGLRenderWindow (01A9F02C): end finalize
> 
> Debug: In c:\Builder\Sources\VTK\Common\vtkObject.cxx, line 130
> vtkObject (01A9F02C): Destructing!
> 
> 
> The error does not occur in a Borland C++ Builder (5 or 6) app having only one 
> vtkBorlandRenderWindow component.  In the case of an app with two such
> components, when the app destroys the components, the first internal render window
> successfully completes its Delete() while the second produce the above errors.
> I'm unsure how to fix this for Borland users (including myself!).  

Urgh... unless my memory is playing tricks again, each RenderWindow
should have a valid context, so that MakeCurrent should actually never
fail.  Does vtkBorlandRenderWindow simply inherit from
vtkWin32OpenGLRenderWindow?

Mathieu, do you have any comments?

-- 
charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/