Michel Dänzer wrote:
It would cover up some of the worst problems - basically the Xlib drawing to a glX window would only show up every second frame...On Mit, 2003-01-08 at 17:04, Keith Whitwell wrote:What "clobbering" is allowed can be inferred from the GLX specification. If you overlook DBE for a second, I believe we are meeting the requirements of the spec, so I wouldn't say we're "broken".This isn't true.
Consider when a diagonal line is drawn by Xlib across the active GL window, with pages flipped.
--> Xlib draws in the "back buffer"
--> Shadow copies the bounding box of the line to the front buffer, including *all* of the backbuffer.
What you really want is just a line to be drawn in the front buffer, but in fact you get a whole lot of garbage with it.
A common place things like this occur is in opaque window moves -- if you move the 3d window when pages are flipped, its contents are replaced with whatever's in the backbuffer.
That only affects the 3D window though, right? The problem I'm trying to solve here is the permanent 2D corruption outside the 3D window. It's fixed in my testing, but I may well not have tried hard enough to break it, more testing is always appreciated. As for inside the 3D window, I'd like to know if this breaks things that work without page flipping but are supposed to work. If so, I'll revert page flipping to be disabled by default. Oh, and we still don't exclude the 3D window in the shadowfb copies, do you think that would be any help?
I don't know how many apps mix xlib and glx -- probably not a huge number.
Keith
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
