https://bugs.kde.org/show_bug.cgi?id=348156
--- Comment #22 from Thomas Lübking <thomas.luebk...@gmail.com> --- (In reply to jeremy9856 from comment #21) > I mean a checkbox easily discoverable, like the one "unredirect windows" It actually was the dedicated intention of the HIG team to stash this particular dialog. > in their own windows and for a "normal" user it's not really obvious that in > order to play game in good condition he need to activate a script in this > particular window. He doesn't - the game can signal its demands and the user can setup a rule (as you originally intended to do, just that you could not match "all fullscreen windows" there) Bear in mind that yours really is a corner case from all I can say about our regular userbase. It might be possible (should b? Really no idea) to make the scripts searchable in systemsettings (so "game" would find you "game mode" if installed) and maybe they should be renamed "extensions" (to align the popular browser concepts)? > The suggestion of Martin is "When a fullscreen game starts, it can create a > “sub-session” That's a brainstorm on how games could be implemented on/next to Wayland. You will neither be able to unredirect nor suspend compositing on wayland, so this may require a completely new infrastructure anyway and is completely unrelated to your concern. > By the way I see that you have submitted a review request > https://git.reviewboard.kde.org/r/126561/ Does this mean that it will be > implemented? It /is/ implemented (and a good sandbag died for it), but the patch not yet approved. Interestingly, the property seems just as much unused as the original KDE property (at least I couldn't find a testcase) -- You are receiving this mail because: You are watching all bug changes.
