On Sat, 2 Feb 2002, Harold L Hunt wrote:
The problem is that XNextEvent () is a blocking function, just like Win32's
GetMessage () function. The problem here is when the X Server exits or
resets while XNextEvent () is blocking... in that case our X Client
(xwinclip) gets no notification
man XSetIOErrorHandler:
The XSetIOErrorHandler sets the fatal I/O error handler.
Xlib calls the program's supplied error handler if any
sort of system call error occurs (for example, the connec
tion to the server was lost). This is assumed to be a
On Sun, 3 Feb 2002, Brian Genisio wrote:
I am not sure that would be the best programming practice... (I could be wrong)
Wont that leave the IOErrorHandler function call still on the stack, causing
problems on multiple restarts of the server?
Or does that setjmp/longjmp change the
Please send your questions to [EMAIL PROTECTED]
Error can mean many things. Were your server up and running? Send further
replies to list.
Suhaib
-Original Message-
From: Eurico Covas [mailto:[EMAIL PROTECTED]]
Sent: Sunday, February 03, 2002 6:46 PM
To: [EMAIL PROTECTED];
