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

List:       kde-bugs-dist
Subject:    [kwin] [Bug 252817] KWin crashes on intel/mesa glClear(GL_COLOR_BUFFER_BIT)
From:       Thomas Lübking <thomas.luebking () gmail ! com>
Date:       2013-07-28 17:55:48
Message-ID: bug-252817-17878-uTVeApoPGn () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=252817

--- Comment #204 from Thomas Lübking <thomas.luebking@gmail.com> ---
(In reply to comment #203)

> And most old games are using SDL 1
Even if, that's irrelevant.
Actually that would make the solution *extremely* simple: have SDL1 tag the
window as "_NET_WM_BYPASS_COMPOSITOR", "1" - problem solved.

> which does override_redirect.
You are aware that "override_redirect" just means: "Dear WM, please ignore me"?
Every popup and tooltip, many docks, some "fullscreen" windows of all sorts
(often because they're just popups), a whole bunch of synthetic windows and
whatnot are.
It's not somehow a hint on the content of the window or some SDL exclusive.
The state is not a usable hint on whether compositing should be used. You enter
the field of heuristics what means you'll hit false positives for sure.

> Regular clients don't need to say anything, they won't be
> unredirected/compositing won't be suspended.

I think there's a misunderstanding about "regular" - i was only talking about
"override_redirect windows that are not interested in skipping the
redirection", NOT about "non override_redirects".

> > And why esp. those which are override_redirect and thus often don't set any
> > properties at all?
> You answered yourself:
No, where?

> It's not too hard to set this hint, 3 lines of code with Xlib or a bit more
> with xcb.

The problem is not that it's hard to do, the problem is that nobody does and
especially you can not expect "legacy" clients to alter to match your
reconsiderations about the protocol.
Providing the ability to hint this preference is fine, but an absent hint only
indicates an absent hint - not any intention.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]