On Wed, Jun 1, 2011 at 2:57 AM, richard boaz <ivor.boaz@xxxxxxxxx> wrote: > hi lothar, > really, you should know the subject deeper before making absolute > statements, for otherwise you run the risk of being wrong and just looking > silly. > multi-threading is primitive with GTK? are you crazy? if you refer to > drawing with Pango, then yes, this must be done in the main thread (when > using X11 backend), but locking all of GTK? you might not be aware that the basic threading model underlying the windows GUI API is very different than the one on X11. windows APIs tend to assume multithreadedness, which results in details like "only the thread that created a window may process events for it". they have implicit locks all over the place to make sure that multithreaded stuff works with not much effort on the part of the programmer (who can still mess it up quite easily). X11 APIs tend to assume single threadedness, don't care what thread does what and have no implicit locks anywhere, meaning that the application must take care to do any necessary locking and synchronization itself. GTK does try to hide these very fundamental differences, and does a prettyreasonable though not perfect job of it. --p _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
