Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!seismo!sundc!pitstop!sun!amdcad!ames!pasteur!ucbvax!decwrl!hplabs!hpda!hpycla!ascgw!fgw!flab!ayumi!yuki From: yuki@rei.stars.flab.Fujitsu.JUNET (Hiroyuki YOSHIDA) Newsgroups: comp.windows.x,fj.windows.x Subject: Another problem in XtDispatchEvent (X11R2) Message-ID: Date: 24 Oct 88 02:35:36 GMT Article-I.D.: rei.YUKI.88Oct24113536 Sender: news@ayumi.stars.flab.fujitsu.JUNET Organization: Fujitsu Laboratories Ltd., Kawasaki, Japan. Lines: 20 When a button is pressed on a non-widget window, XtDispatchEvent may cause a segmentation fault. In such a case, XtDispatchEvent will try to dispatch the event to a modal widget. However, if it can't find any appropriate widget (especially when the modal cascade is empty), it *continues* the usual process. Then, an access to the corresponding widget will cause a segmentation fault. Is this a bug or a feature? Am I to blame for it? I want to allow my users to specify dynamic resizing of subwindows. Of course, I could leave it to the window manager. But, since I hate to allow them to move, hide, or iconify subwindows, I wrote my own code which used XDrawSegments to draw the skeleton of a subwindow. An extra click before erasing the skeleton causes that problem. -- Hiroyuki Yoshida yuki@flab.Fujitsu.JUNET yuki%flab.Fujitsu.JUNET@uunet.uu.NET