[comp.windows.x] the destroy class procedure of CoreWidgetClass

yuki@rei.stars.flab.Fujitsu.JUNET (Hiroyuki YOSHIDA) (10/07/88)

swick@athena.mit.edu ("Ralph R. Swick") said:
> Ok.  I've relented.
Thank you for your quick response.

Let me complain of another problem.

When I destroied a widget which have a pop-up child, the X server 
detected an error, "not a valid window ID", and exit(1).

Hacking the source codes again, I found that the destroy class 
procedure, CoreDestroy, calls XDestroyWindow on every pop-up child 
even if the child has no window!

Is it a known bug? Otherwise, is there any reason?

(I hope I need no hacking :-)
--
Hiroyuki Yoshida
yuki@flab.Fujitsu.JUNET
yuki%flab.Fujitsu.JUNET@uunet.uu.NET

swick@ATHENA.MIT.EDU (Ralph R. Swick) (10/10/88)

> Hacking the source codes again, I found that the destroy class 
> procedure, CoreDestroy, calls XDestroyWindow on every pop-up child 
> even if the child has no window!

This has been fixed in R3.