[vtkusers] RenderWindow question...

[Tuhin]

Nick,

  I hesistate to say much with any authority, but if you are having the user 
open and close the multiple windows I don't think the vtkXOpenGLWindow 
Destructor is being called upon closing.  So it may be the cause of the 
memory leak.  I'm doing some snooping right now... if I can confirm my 
suspicions I will write with more info.  Until then let's hope the VTK gods 
get back to us. :)

Tuhin

On Thursday 27 February 2003 14:47, N Smethurst wrote:
> Hi Tuhin
>
> I am a total novice when it comes to x-windows programming, but I wanted to
> ask if you could expand on the implications of this, specifically could
> this have anything to do with the memory leaks that we have been
> experiencing when opening and closing muliple render windows?
>
> Nick
>
> Le Jeudi 27 Février 2003 21:06, Tuhin a écrit :
> >   I'm having a vtkXOpenGLRenderWindow problem.  It seems that when a user
> > deletes the window the link between the window and VTK isn't cut.
> > Specifically, vtkXOpenGLRenderWindow::Mapped is not reset and
> > vtkXOpenGLRenderWindow::WindowId is not set to 0x0.  Thus, when a
> > Render() call is made to the window (after the user has deleted the
> > window) I get a SIGPIPE.  I have done a little X programming in the past
> > and have used WM events (i.e. WM_DELETE_WINDOW) to tell me when my window
> > was being destroyed. I looked through the VTK nightly source and I
> > couldn't find any classes that used WM_DELETE_WINDOW or the call
> > 'XSetWMProtocols' function that one uses to set WM event notifications.

-- 
Graduate Research Assistant
Dept. Of BME
Vanderbilt University
615-343-8261