Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!ncar!mephisto!mcnc!decvax.dec.com!deccrl!bacchus.pa.dec.com!decwrl!klee
From: klee@wsl.dec.com (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: XSetErrorHandler question
Message-ID: <1990Aug30.182434.2753@wrl.dec.com>
Date: 30 Aug 90 18:24:34 GMT
References: <9008291546.AA05946@thyme.jpl.nasa.gov>
Sender: news@wrl.dec.com (News)
Reply-To: klee@wsl.dec.com
Organization: DEC Western Software Laboratory
Lines: 15


In article <9008291546.AA05946@thyme.jpl.nasa.gov>, kaleb@THYME.JPL.NASA.GOV
(Kaleb Keithley) writes:
|> But in my real program I am seeing the error handler 
|> called once for every four or five events sent to invalid windows.

Unless you're doing something weird, like creating new Xlib errors
inside Xlib error handlers or signal handlers, Xlib should report every
error to you.  A test program I wrote (using DECwindows Ultrix Xlib)
correctly caught each of 100 errors I generated.

Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@wsl.dec.com
uucp: uunet!decwrl!klee