* Michel Dänzer wrote: > On Mon, 2006-10-09 at 17:20 +0200, Thierry Reding wrote: > > * Michel Dänzer wrote: > > > On Sun, 2006-10-08 at 18:18 +0200, Michel Dänzer wrote: > > > > On Sat, 2006-10-07 at 21:35 -0400, David Nusinow wrote: > > > > > > > > > Ideally though, just editing currently broken-for-EXA patch so > > > > > that it's only on when XAA is enabled is probably a better hack. > > > > > > > > Indeed. > > > > > > Actually, it should also be verified that disabling offscreen pixmaps is > > > even necessary or a good idea with XAA on integrated chipsets, in > > > particular i[89]xx. > > > > It seems to me that enabling offscreen pixmaps on my 852GM/855GM chipset > > doesn't make a difference, apart from X behaving slightly "different" when > > starting up compiz. It seems like up until compiz starts rendering, the > > windows are offset a little more than with offscreen pixmaps disabled. > > Define 'offset'. I finally got around to trying this myself, and window > updates were regularly missed. So it seems the problem with XAA > offscreen pixmaps for GLX_EXT_tfp is not just about performance but > correctness. I have set compiz to startup when the GNOME session is loaded, and when compiz replaces metacity, there's a short period where the windows (there's an annoying error message that keeps popping up, but unreleted to compiz or AIGLX) and the desktop are different shades of gray and the window with the error message is first positioned in the top-left corner, then suddenly moves up and to the left. But then, after compiz has loaded and starts updating the window decorations and contents all is back to normal. That is if I comment out the XAANoOffscreenPixmaps option. If it is uncommented, the above "transition" doesn't happen. I'm not sure how helpful this is. After compiz is loaded I don't see any strange behaviour or bad performance with or without XAANoOffscreenPixmaps. - Thierry
Attachment:
signature.asc
Description: Digital signature