Possible idea for new feature for plasma keyboard shortcuts. Double tap key bindings, allowing users to bind multiple events to a single key where one event occurs with single tap and another occurs with a quick double tap.
My Example use case was for opening the overview and grid as I wanted to be able to cycle through them (using the cycle shortcut) but when using the kRunner bar in the overview for anything that would not close the overview on completion (i.e. a calculation) I wanted to be able to exit overview with the meta key, rather then cycle into the grid view first (similar to how cycling between overview and app view works in GNOME).
I am not sure about how feasible this would be in plasma currently as might require reworking of how plasma handles keyboard short cut inputs.
Hi! Interesting one - envisioning how folks could use that, one question I’d have is what latency would need to be introduced in handling keyboard shortcuts like that, if they could be set arbitrarily?
No expert here, but as a user, I would suspect that the GNOME-like use case is easier to accommodate smoothly because the double-tap action is naturally coupled with the single-tap action - the first tap begins moving the overview up, and the second tap then slides the overview further up to expose the application menu.
In that case, the system can afford to respond immediately to the first button-press, because the second one doesn’t cancel the action of the first, it just “extends” it, if that makes sense? If the double-tap action isn’t related in that way to the single-tap action, though, then the system shouldn’t respond to the single-tap immediately - single-tap shortcuts that also have double-taps assigned should wait for the “double-tap timeframe” to expire before executing the action.
Just as a hypothetical, if single-tap of a shortcut was “Open Dolphin” and double-tap was “Mute Audio”, then when a single-tap of that shortcut occurred, it would have to wait to make sure a double-tap didn’t occur before actually opening Dolphin - because you probably don’t want to just go ahead and open Dolphin each time you mute.
If that hypothetical is actually how it would need to work, then I’m not necessarily arguing that it should be a deal-breaker - but it does seem like it would scope that feature down to some relatively specific situations?
Curious for yours & others’ thoughts!
1 Like