Linked by Thom Holwerda on Sat 25th Feb 2006 12:59 UTC, submitted by nzjrs
"Yesterday, I got Qt running on top of the Glib main loop. By using the QAbstractEventDispatcher API, I was able to completely replace the entire event dispatching mechanism of a Qt 4 application with less than 600 lines of code. What does this mean?"
Thread beginning with comment 99077
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-01-02
> Oh my. In this day in age of multi-core someone should
> get on that quick! ...or will moving all the processing
> to the videocard solvethis as a side-effect?
X is lot more than graphics. I don't think X needs to be thread-safe, only one thread should do event processing and painting anyway. This doesn't mean that you couldn't use threads in X programs, you can have separate thread for processing data or whatever but only one thread can do the X stuff.