https://bugs.kde.org/show_bug.cgi?id=462702
--- Comment #5 from Andrew Shark <ash...@linuxcomp.ru> --- Yes. Window Actions can run one of three things: arbitrary command, dbus command, simulate keyboard input. See screenshots. In Trigger tab you can choose when to trigger: window appears, window disappears, window looses focus, window gets focus. And you have a list of window match rules (by class, by title, by something called window role (I do not know what it is), by window type). How I used it. I created a rule that match steam games, and when window gets focus, run a command to change my physical monitor color preset to Game. And oppositely, when steam game looses focus, revert monitor preset to Comfort View (yellowish colors). My project is https://gitlab.com/AndrewShark/monitor-commander. The downside is that in trigger tab we do not have trigger by window changing monitor (see Bug 436062) and you have to make the same list of windows to match two times (for the gets focus and for the looses focus). I can agree that maybe such window actions module is not something to be in system settings. Also because of downsides I said above. I happily will implement it in my app/widget, but how can I do it? Is there something like I can listen to window actions from kwin (events like the window with such title just got focus and so on). What is the starting point of programming this? So the resolution of current bug will be Resolved Intentional, right? -- You are receiving this mail because: You are watching all bug changes.
