https://bugs.kde.org/show_bug.cgi?id=348156
--- Comment #18 from Thomas Lübking <thomas.luebk...@gmail.com> --- (In reply to jeremy9856 from comment #17) > (In reply to Thomas Lübking from comment #16) > > you're apparently looking for a way suspend the compositor for all > > fullscreen > > windows but some exceptions, because your fullscreen windows are typically a > > pleathora of games and only in very few specific occasions eg. "fullscreen > > firefox" should execptionally not suspend the compositor. > That is exactly the use case I'm thinking of ! Ok, neither scripting nor rules are ready for this since they only deal with managed clients, but several games (engine) create "fullscreen" windows as an override_redirect window spanning the root geometry (and grabbing input) Notably with a game context in mind, I strongly suggest to abort any approach reg. unredirection and focus on a solution that skips the compositor. The unredirection gain isn't worth it. You still have +1 active GL context and rather heavy usage of texture memory. Redirection or rather texture_from_pixmap caused quite some load in early compositing ages but is neglectable as of today and redirected gl contexts should sync to the compositor. => What needs to happen: 1. port https://git.reviewboard.kde.org/r/111771/ to KWin/5 => bug #357565 2. adapt the gamemode script to support unmanged windows (local version still does. no idea whether I ever published that - worthless w/o above patch, though. Unmanaged clients cannot be matched, only globally toggled) --- 3. add a config GUI to the gamemode script 4. let the user switch between whitelist and blacklist behavior there --- 5. check whether the script should be shipped w/ kwin (which scripts should be anyway?) 6. recheck w/ HIG team why scripting is "hard to use" (hard to find? clicking the GHNS button cannot be harder than setting up a window rule, can it?) -- You are receiving this mail because: You are watching all bug changes.
