[frameworks-kglobalaccel] [Bug 480304] Add support for second stroke shortcuts (feature request)
https://bugs.kde.org/show_bug.cgi?id=480304 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 480304] Add support for second stroke shortcuts (feature request)
https://bugs.kde.org/show_bug.cgi?id=480304 fanzhuyi...@gmail.com changed: What|Removed |Added CC||bulletproofbe...@proton.me --- Comment #12 from fanzhuyi...@gmail.com --- *** Bug 488383 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 480304] Add support for second stroke shortcuts (feature request)
https://bugs.kde.org/show_bug.cgi?id=480304 --- Comment #11 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kglobalaccel/-/merge_requests/105 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 480304] Add support for second stroke shortcuts (feature request)
https://bugs.kde.org/show_bug.cgi?id=480304 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #10 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/2060 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 480304] Add support for second stroke shortcuts (feature request)
https://bugs.kde.org/show_bug.cgi?id=480304 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 480304] Add support for second stroke shortcuts (feature request)
https://bugs.kde.org/show_bug.cgi?id=480304 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added CC||1i5t5.dun...@cox.net --- Comment #9 from Duncan <1i5t5.dun...@cox.net> --- TLDR summary: Brief kde multi-key global hotkeys history and current status, discussion of available user workarounds. FWIW this remains a long-term regression from the kde3 era where multi-key hotkeys worked fine, including even a popup menu after the first one showing configured second-key choices. Only now it's worse, at least on wayland, because unlike X where every app could see the keys entered (including passwords!!) entered on any other app, thereby allowing third-party global hotkey apps, that choice is gone on wayland (where apps other than the compositor only see keys entered while they are in focus) due to its higher security, so a standardized the third-party solution is out (but see option #3 below... and out at least until a wayland protocol extension is agreed that makes it possible, the mechanism by which third-party screenshotting apps can arrange for access to the visual contents of windows of other wayland apps, for instance). Available workarounds: 1) Stick to X and (continue to) use third-party X-based global hotkey solutions. Biggest downside is that X platform support is now second-class and gets less testing, with the problem only getting worse as time progresses, but if you already have other things keeping you on X and already have a third-party X hotkey app setup, this should work reasonably for awhile, anyway. But I'd *not* recommend this to people who haven't setup such an app yet as the timeframe it'll be viable is limited. Upgrade path would presumably be thru #2, below. 2) On wayland, configure "Legacy X11 App Support" (plasma system settings > security & privacy > application permissions) to "Allow legacy X11 apps to read keystrokes in all apps" to "always". Again, use a third-party X-based global hotkeys solution. This should continue to be supported much longer than #1 and is the likely upgrade path thru which people on #1 will move. As such it's much more viable. There's still a security tradeoff in that all X apps will be seeing your wayland keys as well, but security-wise, it's not worse than the X we used for decades, and is at least a step on the way, since wayland apps will at least not see each others keys even if X apps still do. The upgrade path from this will presumably be through #3, once a wayland protocol extension is standardized to make third-party wayland hotkey apps more viable. Meanwhile, this is likely the simplest solution, even if it is someone time-limited (but less than #1). 3) There is apparently at least one wayland third-party hotkey app, but I don't remember the name ATM (egg-something maybe?) and due to wayland's security which would normally break it, I believe it actually hooks into the input stream below wayland (at the /dev/input/* device-file level), which likely requires fiddling with device-file permissions. I've not looked into it further but have been meaning to as in theory that would have many of the same upsides as the #4 choice I took before I knew about this one, with less of the major downside, complexity, tho there'd still be some in getting the permissions correct and just learning its config. Eventually, wayland/XDG will likely standardize a protocol extension to make third-party global hotkey apps work without the degree of permission-changes, etc, now necessary, and there will be more of these third-party wayland-based apps, enough so as long as the compositor implements the extension, much like the existing situation on X, users won't be locked into whatever the desktop natively provides -- or fails to provide. This is thus the eventual ideal target. 4) Take advantage of the insight that multi-key can be seen as sequential keys, not all of which must be processed by the same app-instance, to cobble together a solution out of available components, with plasma only processing the initial hotkey to launch the cobbled-together solution to handle the second and further keys. This is in fact what I did back when the regression first hit with kde4, and what I still do today, altho I've changed the primary component I use since then. (I initially rolled my own bash script for the menu, but eventually switched to pdmenu...) Ideally, this would work like so: Configure a single plasma/kwin hotkey to launch a third-party menu app, which would then see and process the second and subsequent keys as it would then be the in-focus app. If more than one initial launcher keys are configured, each would conceptually launch the third party app as if it were a submenu, since the choice of initial launching key would effectively be the main menu. Unfortunately I didn't find an
[frameworks-kglobalaccel] [Bug 480304] Add support for second stroke shortcuts (feature request)
https://bugs.kde.org/show_bug.cgi?id=480304 --- Comment #8 from Andrew Shark --- In some places it is already possible to assign second stroke shortcuts. For example, in Kate (or other KDE application) in Configure Global Shortcuts in the Alternate column (but not in the Shortcut column). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 480304] Add support for second stroke shortcuts (feature request)
https://bugs.kde.org/show_bug.cgi?id=480304 fanzhuyi...@gmail.com changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 480304] Add support for second stroke shortcuts (feature request)
https://bugs.kde.org/show_bug.cgi?id=480304 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REOPENED|CONFIRMED --- Comment #7 from fanzhuyi...@gmail.com --- It would be nice if there is some sort of visual feedback (like a OSD popping up) when the user presses the first stroke in a multi-stroke shortcut. The OSD could contain options for all possible next strokes. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 480304] Add support for second stroke shortcuts (feature request)
https://bugs.kde.org/show_bug.cgi?id=480304 Andrew Shark changed: What|Removed |Added CC||amanita+kdeb...@mailbox.org --- Comment #6 from Andrew Shark --- *** Bug 481365 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 480304] Add support for second stroke shortcuts (feature request)
https://bugs.kde.org/show_bug.cgi?id=480304 Andrew Shark changed: What|Removed |Added CC||rii...@gmail.com --- Comment #5 from Andrew Shark --- *** Bug 210618 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 480304] Add support for second stroke shortcuts (feature request)
https://bugs.kde.org/show_bug.cgi?id=480304 Andrew Shark changed: What|Removed |Added CC||vedran.fu...@gmail.com --- Comment #4 from Andrew Shark --- *** Bug 161009 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 480304] Add support for second stroke shortcuts (feature request)
https://bugs.kde.org/show_bug.cgi?id=480304 Andrew Shark changed: What|Removed |Added CC||mrud...@kdewebdev.org --- Comment #3 from Andrew Shark --- *** Bug 217833 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 480304] Add support for second stroke shortcuts (feature request)
https://bugs.kde.org/show_bug.cgi?id=480304 Andrew Shark changed: What|Removed |Added Resolution|DUPLICATE |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 480304] Add support for second stroke shortcuts (feature request)
https://bugs.kde.org/show_bug.cgi?id=480304 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED CC||fanzhuyi...@gmail.com Resolution|--- |DUPLICATE --- Comment #2 from fanzhuyi...@gmail.com --- *** This bug has been marked as a duplicate of bug 217833 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 480304] Add support for second stroke shortcuts (feature request)
https://bugs.kde.org/show_bug.cgi?id=480304 --- Comment #1 from Andrew Shark --- This bug I mentioned in the previous message is - https://bugs.kde.org/show_bug.cgi?id=371560#c0 -- You are receiving this mail because: You are watching all bug changes.
