"Jasper St. Pierre" <[email protected]> writes: > That doesn't sound like it would be too much traffic, and any machine could > handle that nowadays.
Right, the question is not 'xeyes' itself, the question is whether removing this optimization would hurt any real applications that might be reshaping their window on a regular basis, and thus generating piles of expose events. Given that the network utilization isn't heavy, applications which carefully collect expose events and perform minimal repaint won't be affected much by this change. However, applications which trust the X server to have done this optimization for them may well repaint their entire contents once for each rectangle. The impact of that would be fairly serious. Just to fill people in on the larger context, this optimization was written with xeyes in mind, but the main need was not from the xeyes application itself, but from other applications on the desktop. In a non-composited environment, imagine dragging xeyes around the desktop and sending millions of expose events to every application. Even if we don't care much about this case now, I'm having a hard time getting excited about removing a fairly benign optimization, even if the resulting code is a whole lot prettier. -- [email protected]
pgpdKhzU0a9l4.pgp
Description: PGP signature
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
