https://bugs.kde.org/show_bug.cgi?id=361091
--- Comment #8 from Thomas Lübking <thomas.luebk...@gmail.com> --- The problem with the hint is: "The compositing manager MAY bypass compositing for both fullscreen and non-fullscreen windows if bypassing is requested, but MUST NOT bypass if it would cause differences from the composited appearance." This can never be guaranteed - an unredirected window shapes away the compositor scene and as result will nearby inevitably impact the result (even for fullscreen windows, some effect - like be::clock ;-) - might simply paint onto the final scene) - that impact not generally detectable. So basically the hint is to be ignored... m( Also, if there was considerable benefit in pure unredirection *and* you could guarantee that this does not impact the outcome, hell just unredirect the window - why look at a property hint itfp? So we put the focus on: "window would benefit from running uncomposited [...] or that the window might be hurt from being uncomposited" which is the reasonable part and also intended by _KDE_NET_WM_BLOCK_COMPOSITING The point is that a heavy GL game errr.... CAD studio!, windowed or fullscreen, will largely benefit from being the only (ok, that one's lost...) active GL context around, notably if you're short on texture RAM. -- You are receiving this mail because: You are watching all bug changes.
