Hi!
I hate to ask this as, looking through the archives, there is a lot on
threading...just not the right stuff :)
I'd appreciate it if someone could post some example code that has two
threads, each constructing its own window (i.e. one gtk.mainloop() per
thread).
The code I have at the moment behaves differently, depending on where i
put the gtk.threads_init() function: sometimes it gives
"
The program received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 3822 error_code 5 request_code 20 minor_code 0)
  (Note to [..snip..] function.)
"
and sometimes it crashed with:
"Xlib: unexpected async reply (sequence 0xf04)!"

Just to ensure:
I have pygtk threads compiled in (Debian Unstable), I am using
gtk.threads_init() (I even tried using it several times in the same
piece of code), I have wrapped the gtk.mainloop() in gtk.threads_enter()
and gtk.threads_leave() (I tried just wrapping one, or wrapping both, no
success in either scenario).

Why do I need to gtk.mainloop()'s ? I want to update a custom dialogue window,
while the main window is doing other stuff. I don't think its a problem
of Lock()'ing things as the code doesn't seem to even get that far
I tried to stick to Cedric Gustin's example code (which works well, even
if I implement it into my programme's main window) as closely as
possible.
Thanks for any reply,
jj

-- 
Wit, n.:
        The salt with which the American Humorist spoils his cookery
        ... by leaving it out.
                -- Ambrose Bierce, "The Devil's Dictionary"

Attachment: signature.asc
Description: Digital signature

_______________________________________________
pygtk mailing list   [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/

Reply via email to