In System Settings -> Shortcuts -> Custom Shortcuts when you create a new Window Action, then when you specify window properties in a list, currently you can only match by title, class, role and type. I would like the ability to also match by a screen the window belongs to. My use case is the following. I have dell monitors, and I like to change monitor's presets depending on application. I am trying to create rules, that kinda replicates the dell display manager application. If I launch a game on first monitor, I want to send a command to first monitor to switch to Game mode. But when I drag the game window to second monitor, I want to send command to the second monitor to switch to game preset and send command to first monitor to switch to standard preset. So I need to know on which monitor the window match happened. What do you think about that idea? Is it a wanted feature there, or I need to find another way to determine that info? Additional info: In Window Management -> Window Rules you can see that there you can set some properties to windows that match some other specified properties. The screen property there is (currently) to override a screen the window will be moved to, but not to match a rule by a screen at which window is currently located. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2
As announced in https://pointieststick.com/2023/07/26/what-we-plan-to-remove-in-plasma-6/ and https://community.kde.org/Plasma/Plasma_6#Removals, I'm afraid KHotKeys has reached end-of-life in Plasma 6. Accordingly, all bug reports and feature requests for it must be closed now. Most of what KHotKeys could do can already be done with the newer KGlobalAccel system in Plasma 6. A few features such as mouse gestures and triggering conditions based on changes to window states are not yet implemented in the new system. These will be added in the future if and when resources materialize for them, and/or when a kind soul submits patches to implement them! :) Meanwhile, the 3rd-party "Mouse Actions" app (https://github.com/jersou/mouse-actions) may be usable for implementing your own mouse gestures again. Thanks for your understanding, everyone.