[PATCH 00/11] Misc window exposure/validation cleanups

[Jasper St. Pierre]

Why would xeyes generate a large number of rectangles in a composited
environment? Are you talking about the initial expose?

On Thu, Sep 18, 2014 at 4:49 PM, Keith Packard <keithp at keithp.com> wrote:

> Adam Jackson <ajax at redhat.com> writes:
>
> > In attempting to get the Always mode of backing store working again, I
> > felt the urge to clean the place up a bit.  The most notable change here
> > is removing the (questionable) optimization from exposure event
> generation
> > to emit a bounding-box event when faced with more than 25 rects in the
> > exposed region.  Given that toolkits already coalesce consecutive expose
> > boxes, and that you'll never hit it in a composited environment anyway,
> > the complexity doesn't seem justified.
>
> This was written to address shaped windows, which can still generate a
> large number of rectangles, even in a composited environment. I think
> xeyes was the original test case; a full-screen xeyes window has a
> couple thousand rectangles, or about 64kB of data.
>
> I suspect an xeyes-specific optimization is not all that useful to keep
> around, but I fear that some user somewhere is taking advantage of this...
>
> --
> keith.packard at intel.com
>
> _______________________________________________
> xorg-devel at lists.x.org: X.Org development
> Archives: http://lists.x.org/archives/xorg-devel
> Info: http://lists.x.org/mailman/listinfo/xorg-devel
>



-- 
  Jasper
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg-devel/attachments/20140919/097acaf1/attachment.html>