On Tue, Feb 03, 2004 at 08:33:11PM -0500, Dave Aitel wrote:Well, that sucks, cause right now pyGTK is a good API for serious multi-platform work. Having it restricted to Linux would seriously hamper my ability to build a product using it...and everyone else's, I assume. And having it not be able to do threads is the same as not being able to work at all.
Is there a known bug, possibly related to threading (I just thread enabled by app), that turns the fonts to white on white, in pyGTK (latest python and pyGTK) on Windows XP?
Probably not related to the topic of this thread, but important for would be multi threaders on Windows. It is almost not possible to use multiple threads safely with gtk on Windows, even if you lock properly. Xlib doesn't care about threads, as long as you serialize your calls properly. Windows is fundamentally different. When you create a window, the window is married to the thread that called CreateWindow. This means it is impossible to use gtk/gdk from different threads even if you lock properly without looking under the gdk hood to see if the underlying Win32 API calls are "safe". You gotta love Windows. As has been discussed on the gtk-devel list a solution is to have GDK create a single thread dedicated to Window creation, and have functions post thread messages to this thread. This would not be trivial to implement.
--jkl
I'm happy forcing my users to run as Admin, if that's necessary.
How is Qt solving this problem?
How hard is it to set up a CVS environment using Cygwin so I can do a complete install of GTK and dropline pygtk on Windows and track down my threading issue in gtk.glade.xml()? Is there a quick guide to this somewhere? I thought I saw one, but then I lost it.
-dave
_______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
