*apologies about the previous incomplete post -- it was sent unintentionally!
I'm having trouble tracking down a printing problem. My code is
hanging when using threads and running the following:
dialog = gnomeprint.ui.Dialog(self.job, self.dialog_title,
gnomeprint.ui.DIALOG_RANGE |
gnomeprint.ui.DIALOG_COPIES,
**self.dialog_kwargs)
The code hangs in a way I've only seen when I have a problem inside a
thread -- I have to kill the process manually (it doesn't respond to a
Control-C interrupt).
My app has a "no threads" mode for Windows -- when running without
threads, gnomeprint works as usual. However, gnomeprint is not being
called from a subthread -- it's in the main gtk thread -- and as far
as I can tell, the fact that threading's enabled has done nothing but
call gtk.threads_init(). This crash happens before any other threads
have started.
That said, I still haven't been able to boil this down to a simple
example -- I thought I'd throw it out here in case anyone had any idea
why gnomeprint might behave badly with threading on. I will, of
course, continue to try to boil this down to a simple test piece of
code.
I'm working on ubuntu hoary.
As reported from python, I'm running:
gtk 2.6.4
pygtk 2.6.0
As reported by ubuntu, I'm running:
python-gnome 2.10.0-0ubuntu1
Thanks for any ideas,
Tom
_______________________________________________
pygtk mailing list pygtk@daa.com.au
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
