Summary: | Global shortcuts involving Ctrl+Shift are not handled | ||
---|---|---|---|
Product: | [Unmaintained] khotkeys | Reporter: | Pavel Gurevich <fax.k.root> |
Component: | general | Assignee: | Michael Jansen <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bleverett |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 4.8.0 | |
Sentry Crash Report: |
Description
Pavel Gurevich
2009-11-17 21:41:19 UTC
I paid attention, that there might be a more general problem: when several modifiers are present, Shift is somehow disregarded. For example, <Win>-<Tab> is set for switching desktops, and <Win>-<Shift>-<Tab> is used for reverse switch. The latter does not work, although is set without a problem in the Control Centre. I have this problem. What seems to be happening is that modifier keys (shift, alt, etc.) do not get registered. I wanted Shift+Media Next to do something, but what showed up in kglobalshortcutsrc was simply "Media Next". I edited the line in kglobalshortcutsrc manually to be "Shift+Media Next", and now the shortcut works. It appears that the global shortcuts editor drops any modifier from the custom input keycode. Git commit 568cb9268a3f940564d155526cb81cec4327cbf6 by Simon Persson. Committed on 29/06/2011 at 04:56. Pushed by persson into branch 'master'. Fix global shortcuts that include symbols produced with shift key KKeySequenceWidget (used to enter shortcuts) removes shift from the recorded shortcut if the symbol produced from that key is different when shift is used. kglobalaccel needs to include shift in the grab in order to be triggered on this class of shortcuts, and then in the keypress event handler it also needs to strip the shift again before checking which shortcut was just triggered. BUG: 179504 BUG: 197548 BUG: 215030 CCMAIL: kde@michael-jansen.biz REVIEW: 101520 M +23 -3 kglobalaccel/kglobalaccel_x11.cpp http://commits.kde.org/kde-runtime/568cb9268a3f940564d155526cb81cec4327cbf6 Which release the patch is intended to be included in, please? I'm running KDE SC 4.7.1@OpenSuSE 11.4, and the bug is still there. |