> this may or may not have anything to do with xforms, but since i
> started using fl_add_io_callback, i've been getting this errror:
> GL: X ext error: major req = 42, minor req = 0, err code = 8
> ERROR #93 Error in communication with window server: ERR_WMANIPC
> [...]
> i'm using fl_add_io_callback to read the output of a popened tail of a file
> (which is my only access to the state of a concurrently running gots
> simulation) perhaps the fact that this is a blocking read means i can't use
> fl_add_io_callback in this application...
I don't see why a blocking read should be a problem unless it blocks
for an exceedingly long time, though I'm not sure why it would block
at all if you're doing processing in the I/O callback correctly.
Why do you need to do a popen()? Wouldn't a plain fopen() be more
desirable if you're just reading a file?
Does this error occur at the same point every time? Is it predictable
in any manner? What's happening with OpenGL when this error occurs?
Are there a lot of transactions?
Are you perhaps looking at the wrong file descriptor? If your
application unintentionally snarfs packets destined for the window
mangler I guess I'd expect to see something like this.
Those are the questions I'd be asking myself, anyway.
spl
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
Xforms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/