Re: A couple of questions about the new order

Around 19 o'clock on Nov 25, "Robert O'Callahan" wrote:

> Here's the thing that I didn't manage to get across, so I'll try again: 
> most of our child windows (except for plugins) don't have their own 
> contents to draw.

So they are effectively "input only"?

> In other words, we'd just as soon treat these child windows as fully
> transparent.

InputOnly windows have no content of their own, the other alternative is 
ARGB windows with zero alpha values.

> If we put these child windows into Manual mode, would there be any problems
> if we choose not to ever repaint these child windows, and never actually
> look at their contents? It seems that at least their backing buffers would
> be sitting there, wasting memory.

If they truely have no intrinsic content of their own, they should be 
InputOnly.

> Also, can we now scroll by just copying pixels within Composite's 
> backing pixmap for a window?

You could always do that using CopyArea in IncludeInferiors mode, the 
trick was that the child window position wouldn't get set correctly.  Now, 
with Composite, you can avoid having child window updates have any affect 
on the parent.

> So when a timeout fires, it just looks ugly? I guess that's OK.

That's likely; given suitably long timeouts, they "shouldn't" ever occur 
if applications are keeping up.  In the normal course of events, I'd 
expect updates to be triggered when all affected windows are ready.  Note 
that none of this has seen any more exposition than you've read here.

-keith