[kwin] [Bug 442219] Hotkeys + Window shortcut rules
https://bugs.kde.org/show_bug.cgi?id=442219 Martin Kimmerle changed: What|Removed |Added CC||d...@256k.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442219] Hotkeys + Window shortcut rules
https://bugs.kde.org/show_bug.cgi?id=442219 --- Comment #8 from Dominik Kummer --- @Ismael I think the icons-only task manager is focused more on mouse usage. Now I use Meta+Alt+D to launch Dolphin instance and Meta+D to focus first instance. Having Meta+D cycle focus multiple instances, or launch a new instance if no instance is launched, could shorten the formula. But this can be solved with Custom Shortcuts and scripts also. Could Custom Shortcuts Settings be the right place to manage more specific shortcut behavior? (KWin Rule Shortcuts should btw also be transparently listed there.) Besides "Global Shortcuts" it is already possible to define "Window Actions" there. But right now it is not possible to Trigger Window Actions with Global Shortcuts. I think that is the missing link which is currently implemented with Window Rules Shortcut. I like the idea of "visual scripting" dbus methods, thats what Custom Shortcuts is already aiming for I guess. ps: sorry for spamming, I just forgot about this bug report *facepalm* -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442219] Hotkeys + Window shortcut rules
https://bugs.kde.org/show_bug.cgi?id=442219 --- Comment #7 from Ismael Asensio --- *** Bug 442220 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442219] Hotkeys + Window shortcut rules
https://bugs.kde.org/show_bug.cgi?id=442219 --- Comment #6 from Ismael Asensio --- *** Bug 444675 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442219] Hotkeys + Window shortcut rules
https://bugs.kde.org/show_bug.cgi?id=442219
--- Comment #5 from Dominik Kummer ---
> The shortcut is registered when a window matches a rule, and de-registered
> after that, so it cannot launch the application itself. This explains
> why the single letter ("K" in the example) appears as text, as there
> is no shortcut when that happens.
I see, but though a "already known" hotkey definition, which has temporarly no
effect because no Window/Application currently matches the rule, should not
write any character which is part of this hotkey. It contradicts the intention
of the user.
The "cycle focus" behavior would be tightly related to kwin rules, because
multiple windows can match a single rule. Like "if focused window matches the
rule where shortcut is defined, and this specific shortcut is pressed again,
then focus on next matching window". Unfortunately I have no clue how to
implement this behavior right now.
I think this behavior could be intuitively expected, and is a huge advantage
(it could save shortcut combinations for other purposes)
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 442219] Hotkeys + Window shortcut rules
https://bugs.kde.org/show_bug.cgi?id=442219
Ismael Asensio changed:
What|Removed |Added
Component|kcm_kwinrules |rules
Product|systemsettings |kwin
--- Comment #4 from Ismael Asensio ---
I don't know exactly how to triage this bug. What it depicts is true, but it is
also kind of intended behavior.
The window rules are attached by definition to specific windows, not
applications. In case of an activation shortcut rule, it lacks information
about the application itself, it just knows the actual window.
The shortcut is registered when a window matches a rule, and de-registered
after that, so it cannot launch the application itself. This explains why the
single letter ("K" in the example) appears as text, as there is no shortcut
when that happens.
If we wanted some shortcut to show this behavior (cycle focus between open
instances of an application, or launch a new instance otherwise) I think a more
proper place might be the Icons-Only Task Manager. This sounds to me a lot just
how icons for pinned apps work, but I'm not sure as I don't use that workflow.
About cycling between open windows matching the rule, this is a valid feature
request, but would require some "deep" changes on how the shortcut is handled
by kwin. It has also been requested in
https://bugs.kde.org/show_bug.cgi?id=442220
--
You are receiving this mail because:
You are watching all bug changes.
