Didier Verna wrote:
I don't understand why you're trying to twiddle the app
context. Isn't
XtCloseDisplay enough to solve the problem ?
If it's safe to call XtCloseDisplay in this situation, then yes.
XtCloseDisplay calls XtDeleteFromAppContext, so if you can call
XtCloseDisplay without it freaking about the fact that the display is
defunct, than that should solve the problem.
Hmm. Using XtCloseDisplay in the test case seems OK, although I don't
know if a more complex case (e.g. XEmacs) will present problems. I
would have thought that of XtCloseDisplay performs Xlib calls, the
error handler will be re-invoked.
I think that the only sure way to find out is to add the necessary
code to XEmacs and bang on it some.
--
Glynn Clements <glynn(a)sensei.co.uk>