Path: utzoo!attcan!uunet!kddlab!titcca!fgw!flab!ayumi!yuki From: yuki@rei.stars.flab.Fujitsu.JUNET (Hiroyuki YOSHIDA) Newsgroups: comp.windows.x,fj.windows.x Subject: the destroy class procedure of CoreWidgetClass (X11R2) Message-ID: Date: 7 Oct 88 07:16:22 GMT Sender: news@ayumi.stars.flab.fujitsu.JUNET Organization: Fujitsu Laboratories Ltd., Kawasaki, Japan. Lines: 20 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