| Summary: | Allow active screen edges to control volume | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Thomas Vde <ThomasvonderElbe> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Thomas Vde
2018-11-02 09:12:22 UTC
This is a classic case for KWin scripts. You can bind screen edges in a script and from there control volume through dbus calls. But this is nothing which should be added to KWin in general. It's a too specific personal use case. Thank you Martin, for your reply and your hint! Now before I get into KWin-scripting (I am not a programmer (yet)), can you confirm, that through this avenue, I could not just trigger one single event, like launching a program for example, but a whole series of actions ... because scrolling up and down in a hot corner without moving the cursor ... would be sort of many events in succession? If you could clarify this for me, that would be really appreciated! The screenedge functionality always triggers only one event. E.g. you could trigger and it mutes, trigger again and unmute. Our screen edge functionality is movement based, we neither support clicks nor wheel. That's a pity! But thanks for clarifying! |