Summary: | Impossible to use tab as custom shortcut anymore | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Daffa Mumtaz <daffamumtaz2001> |
Component: | kcm_keys | Assignee: | Michael Jansen <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alexander.lohnau, christ.derek, jogeshsriram, kde, kdebugs.undead, kdelibs-bugs, nate, noahadvs, plasma-bugs, the.neophytes.logs, wjake1324 |
Priority: | VHI | Keywords: | regression |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=423305 | ||
Latest Commit: | https://invent.kde.org/frameworks/kcmutils/commit/8ac50dd36e5a9d33ffdb5e3ca4fcf67516263da9 | Version Fixed In: | 5.75 |
Attachments: | Screenshot of custom shortcut with tab |
Description
Daffa Mumtaz
2020-06-17 03:32:14 UTC
I can confirm that this issue exists. Created attachment 129584 [details]
Screenshot of custom shortcut with tab
I'm not able to reproduce this issue on my machine. I have attached a screenshot in the previous comment. Maybe it's a regression? Here's my system information if it helps: Operating System: Manjaro Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 (In reply to Oussema Bouaneni from comment #3) > I'm not able to reproduce this issue on my machine. I have attached a > screenshot in the previous comment. Maybe it's a regression? > > Here's my system information if it helps: > > Operating System: Manjaro Linux > KDE Plasma Version: 5.18.5 > KDE Frameworks Version: 5.70.0 > Qt Version: 5.15.0 Yes it's a regression to the new Global Shortcuts UI in 5.19 *** Bug 423399 has been marked as a duplicate of this bug. *** *** Bug 423581 has been marked as a duplicate of this bug. *** To give you a workaround: It works with kmenuedit (In reply to Alexander Lohnau from comment #7) > To give you a workaround: It works with kmenuedit How exactly do I change KWin > Switch to Next Desktop shortcut to Meta + Tab from kmenuedit? Application shortcuts are also affected by this bug and for that kmenuedit works as a perfect workaround (should have maybe been more clear about that). But you could just manually edit the ~/.config/kglobalshortcutsrc file and go to the the "[kwin]" group and edit/add the following entry: Switch to Next Desktop=Meta+Ctrl+Tab,none,Switch to Next Desktop And then logging in and out to restart the affected apps. It works great for me :) Application shortcuts are also affected by this bug and for that kmenuedit works as a perfect workaround (should have maybe been more clear about that). But you could just manually edit the ~/.config/kglobalshortcutsrc file and go to the the "[kwin]" group and edit/add the following entry: Switch to Next Desktop=Meta+Ctrl+Tab,none,Switch to Next Desktop And then logging in and out to restart the affected apps. It works great for me :) That is because the new Global Shortcuts UI uses QML. The old QWidgets one had an extra case to prevent the focus loss with tab/backtab: https://invent.kde.org/frameworks/kxmlgui/-/blob/master/src/kkeysequencewidget.cpp#L675 But I don't know how to implement this behavior in QML. With gammaray we coudl maybe check what gets the tab event. Maybe the kcm can install an eventfilter or something *** Bug 424947 has been marked as a duplicate of this bug. *** Moving back to the kcm, the keysequenceitems in plasmoid shortcut settings are not affected. I think it may have something to do with qquickwidget because it also works correctly with plasma-settings. Git commit 8ac50dd36e5a9d33ffdb5e3ca4fcf67516263da9 by David Redondo. Committed on 18/09/2020 at 09:11. Pushed by davidre into branch 'master'. Remove handling for inside events from tab hack The hack broke KeySequenceItem. I tried removing it entirely with "activeFocus:true" of the root item but from my testing we still need this reduced hack to go outside of the qquickwidget while tabbing around. M +14 -41 src/kcmoduleqml.cpp https://invent.kde.org/frameworks/kcmutils/commit/8ac50dd36e5a9d33ffdb5e3ca4fcf67516263da9 *** Bug 427125 has been marked as a duplicate of this bug. *** |