Charlie Von Metzradt wrote:
Hello,
I'm writing a multithreaded application, and I'm getting some xlib errors:
Xlib: unexpected async reply (sequence 0x813d9)!
I've done my homework and found that these are caused by modifying the GUI from threads other than the main one. I've fixed any place where I was doing this, but I'm still getting these errors. I'm not sure where to look next, I need another way of tracking down what I've done wrong.
Apparently, the best way to locate the source of the errors is to put the X connection into synchronous mode, which will tell you what call/operation caused it. The trouble is, I can't find any way of putting wx into synchronous mode. I've even searched the wxwidgets/wxpython source, and it doesn't appear to support this operation.
I've tried looking for a way to put the entire X server into synchronous mode, but I have had little success with that too.
Does anybody have any ideas?
Any command-line args that are given to the app (wxPython automatically takes the sys.argv strings and passes them to the app initialization functions) are passed on to the gtk_init() function, which also passes them to the xlib init function, so you should be able to use standard X11 and GTK command line args. So for putting the app into synchronous mode try --sync.
ยทยทยท
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!