Linked by Thom Holwerda on Sun 4th Jun 2006 13:01 UTC
Thread beginning with comment 130540
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.





.
Member since:
2005-07-06
GTK+'s redraw is actually fairly well-optimized. It's just optimized for the wrong thing. GTK+ has a habit of trying to batch and coalesce EXPOSE events. This cuts down on overall CPU usage, but increases latency, leading to visible redraw.
Of course, ultimately, a composited desktop is the only correct solution to the redraw problem. It also has the advantage of allowing the toolkit to optimize for minimal CPU usage, since the compositor ensures that redraw latency (with reasonable bounds), doesn't result in visible artifacts.