[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwin
Subject:    Re: Why custom flushBuffer code?
From:       Thomas =?iso-8859-15?q?L=FCbking?= <thomas.luebking () gmail ! com>
Date:       2010-12-01 20:50:42
Message-ID: 201012012150.42611.thomas.luebking () gmail ! com
[Download RAW message or body]

tried
flushBuffer()
        waitSync();  // 1. iteration
        glXSwapBuffers( display(), glxbuffer );  // 1. iteration
        glXWaitGL(); // 2. iteration
        XFlush( display()); // 2. iteration
        return;
paintBackground()
	return;

and it flickers like hell (direct/indirect rendering, vsync on/off, flipping 
or not) - paintbackground is presumingly only required if there's no desktop 
widget present? (didn't try)

Thomas

Am Wednesday 01 December 2010 schrieb Martin Gräßlin:
> Hi,
> 
> can anyone explain me why we need the code in
> void SceneOpenGL::flushBuffer( int mask, QRegion damage )
> for double buffering?
> 
> I just tried to implement it with ES and none of the used API calls is
> present. There is neither an equivialent to glxCopySubBuffer nor the
> glBitmap/glCopyPixel combo.
> 
> So my ES code is currently running without anything in paintBackground and
> without anything in flushBuffer except eglSwapBuffer. And it's working
> fine. I cannot notice any problems.
> 
> So if there is no reason for that code, I would dare to remove the
> flushBuffer and paintBackground code. This should improve the rendering
> quite a lot as it's many glScissor followed by single quad painting.
> 
> Cheers
> Martin

_______________________________________________
kwin mailing list
kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin

[prev in list] [next in list] [prev in thread] [next in thread]