Re: A couple of questions about the new order
Keith Packard <[email protected]>
| Newsgroups | gmane.comp.freedesktop.xserver |
|---|---|
| Message-ID | <[email protected]> |
Around 22 o'clock on Nov 25, Robert O'Callahan wrote: > It sounds like InputOnly windows should solve our problem pretty well as > long as they can have regular InputOutput children. Thanks for the tip! Nope, InputOnly windows can only have InputOnly windows as children, but again, if the parent is in Manual update mode, then nothing appears on the screen for any of the children until the parent contents are copied up to the grandparent. > Good. There is still a double-buffering issue; we don't want the > XCopyArea to be visible until we've also painted the newly exposed area > (currently we have huge hacks to mitigate this). That reduces to the > issue of how do we tell Composite that we're done rendering a frame. If you're in Manual update mode, you tell Composite you're done by copying the window to it's parent (in IncludeInferiors mode). Simple, and under the client's control. -keith