Path: utzoo!attcan!uunet!husc6!bloom-beacon!ZERMATT.LCS.MIT.EDU!RWS
From: RWS@ZERMATT.LCS.MIT.EDU (Robert Scheifler)
Newsgroups: comp.windows.x
Subject: Need Help on XESetErrorString
Message-ID: <19880617123028.5.RWS@KILLINGTON.LCS.MIT.EDU>
Date: 17 Jun 88 12:30:00 GMT
References: <26900040@uiucdcsm>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 12

The I/O error handler is controlled with XSetIOErrorHandler.
This cannot be controlled per-extension.

XESetErrorString is for generating error strings for new errors defined
by extensions.  It is not for I/O errors (the comment in Xlib is
incorrect).  Note that *all* handlers are called for *every* error, even
core ones; your handler needs to check the error code to see if it is
"yours" and generally do nothing if it isn't.

XESetFlushGC is used to define a handler to be called whenever Xlib
forces its internal cached state of a GC out to the server.  It has
nothing to do with errors.