[vtkusers] Bug in vtkDataArray.cxx; was: Bug in vtkWin32OpenGLRenderWindow when using own Interactor and windowhandle

[Roland Schwarz]

> > Therefore it seems logically to me that the RenderWindow should keep
> > hands
> > off this resources when destroying the window.
>
> Except for the fact that we are in the RenderWindow destructor, which
> means we are destroying the RenderWindow while the Win32 window may stay
> alive. The  ren->SetRenderWindow(NULL) should ALLWAYS be called when the
> RenderWindow gets destroyed.
>

Of course. You are right. Didn't consider this. But as you already stated
perhaps the best would be to break up Clean() to handle the vtk things and
Win32 things separately.

Lets hope some of the developers, will take our point.

Regards,
Roland