On Mon, Nov 08, 2004 at 06:52:57AM -0500, Thomas Mills Hinkle wrote: > Okay, so I think between this and the other thread, I'm gathering that > gtk.threads_enter() and gtk.threads_leave() will not keep me safe, and > that the recent bug I found is the first of many I may have to encounter > over the life of my app,esp. if I port it to Windows. > > So I'm going to add learning-about-queue's to my to-do list and hope > that that makes my threading woes go away. I probably won't get to this > until the weekend. The bit of sample code Tim Evans posted in response > to Jamie Norrish's problem will help me get started. Are there other > queue examples that I've just missed i.e. in the FAQ? If not, perhaps > it would be worth piecing one together and referencing it in the section > of the FAQ that describes gtk.threads_enter() and other alternatives > (generators, weightless threads).
Well not strictly a queue although with similar behaviour, you can have a look at the thread demo program I posted to this list some time ago. http://www.mail-archive.com/[email protected]/msg08663.html Since you write about porting to windows, I would really appreciate it if you could test this program under windows and report on how it behaves. The program was written with various remarks about windows and threading in mind, so it should work, unfortunatly I don't have a window machine at my disposal where I could test this code myself. -- Antoon Pardon _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
