Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!snorkelwacker.mit.edu!bloom-beacon!dont-send-mail-to-path-lines
From: converse@expo.lcs.mit.EDU
Newsgroups: comp.windows.x
Subject: Re: XtDestroyWidget bug?/problem/question
Message-ID: <9103222203.AA01672@excess.lcs.mit.edu>
Date: 22 Mar 91 22:02:57 GMT
References: <9103222135.AA03192@madison.ivy.isc.com>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 7


Phase 2 of the destruction of a widget, which includes destroying
the widget's window and freeing all memory associated with the widget,
does not occur until the current invocation of XtDispatchEvent is
about to return.  When you write a loop to create and destroy 
widgets within a callback, phase 2 of destruction of all those
widgets is not executed until the callback completes.