Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!ATHENA.MIT.EDU!swick
From: swick@ATHENA.MIT.EDU (Ralph R. Swick)
Newsgroups: comp.windows.x
Subject: Re: XtDestroyWidget
Message-ID: <8810251225.AA25972@LYRE.MIT.EDU>
Date: 25 Oct 88 12:25:03 GMT
References: <100920021@hpcvlx.HP.COM>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: DEC/MIT Project Athena
Lines: 17

> Date: 24 Oct 88 21:17:03 GMT
> From: hp-pcd!hpcvlx!fred@hplabs.hp.com  (Fred Taft)
> ...
> The next time you make
> a call to XtNextEvent (directly or by means of XtMainLoop), the first thing
> it does is check to see if there are any widgets waiting to be destroyed.

Yes, this is the way Release 2 implemented the requirement that
(Section 4.7) "Phase two occurs when all procedures that should execute as a
 result of the current event have been called."

It was recognized (and documented) that this implementation was not
completely satisfactory and it has been changed for Release 3 in a way
similar to that
described in "Issues 1 and 2" in the referenced section of the R2 documentation.
In R3, when a call to XtDispatchEvent returns, all XtDestroyWidget calls made
within that invocation of XtDispatchEvent will have completed.