Q: Xserver / Composite behavior

[Carsten Haitzler (The Rasterman)]

On Sun, 08 Jan 2006 14:03:00 +1100 Russell Shaw <rjshaw at netspace.net.au>
babbled:

> Amir Bukhari wrote:
> > 
> >>Keith Packard wrote:
> >>
> >>>On Sun, 2006-01-08 at 01:46 +0100, Amir Bukhari wrote:
> >>>
> >>What happend when application move it's top level window 
> >>out side root window. Example: screen is 1200x1024 and a window is moved 
> >>to 1600,512 which out side screen. Does Xserver will not alow it or it 
> >>will only not be visable? does Xcomposite will stil render to off-screen
> >>pixmap?
> >>>
> >>>The entire contents of the redirected window are always available, 
> >>>independent of position or stacking.
> >>
> >>Isn't that a bit inefficient? If you had a 1000x1000 window 
> >>scrolled outside the root, it'd be wasting 4MB in a useless 
> >>pixmap. No wonder X is so slow;) 
> > 
> > It will not be wasted, because the pixmap still be used in our 3D enviroment
> > (LG).
> 
> Hopefully it won't be wasted by default in 2D environments.
> Offscreen memory should only be used for explicitly created
> pixmaps or double-buffered windows.

a composite manager environment IMPLICITLY makes all composited windows double
buffered by definition of its functionality.

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    raster at rasterman.com
裸好多
Tokyo, Japan (東京 日本)