You can always inform the GUI thread to update by using idle timers or asycronous queues. (both are in glib)
Thanks, I know in programming there's always a few ways to do the same thing, that's not really what I'm asking.
I'm just curious about a clear explanation where they're heading to, what's the upcoming threading model and why those decisions. gdk_threads_enter/leave work just fine, and are better in the sense that my source code is less fragmented e.g. doesn't have to be scattered across extra methods.
So I wonder are they just trying to force programmers to use only one threading approach or are there serious technical difficulties supporting gdk_threads_enter/leave, or maybe something else.
Bookmarks