Summary: | Unable to use Meny key in shortcuts | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Magnus Johansson <johanssongreppet> |
Component: | shortcuts | Assignee: | Michael Jansen <kde> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | kwin-bugs-null |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian stable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Magnus Johansson
2010-05-14 13:39:44 UTC
what is the menu key? keycode 115 ("mod4" the key between left ctrl and alt, probably has a windows logo) is a meta key (iirc always has been) you'll have to eg. modmap it to another key (like F13, as you probably don't have F13-F20) if you want to use it as full key try "xmodmap -e "keycode 115 = F13", then try assign this key to whatever. (you can automize this via eg. ~/.kde/share/autostart/ add a file "xprofile.desktop" -- snip -- [Desktop Entry] Exec=/bin/sh $HOME/.xprofile #Hidden=true Name=xprofile Type=Service X-KDE-StartupNotify=false X-KDE-autostart-phase=0 -- end snip -- and "$HOME/.xprofile" containing the above command or xmodmap ~/.Xmodmap (which you'll have to fill with the required aliases, at least "keycode 115 = F13" (w/o the quotes) Thomas, the Menu key has a small image of a drop-down menu and a mouse pointer arrow on it, and the key is most often placed to the left of the right Ctrl key. Its key code is 117. ... and keysym 0xff67, you're right. Qt seems to (internally) bind it to the context event (ie. you get the rmb instead, i was not able to add it by editing kglobalshortcutsrc) (In reply to comment #3) > ... and keysym 0xff67, you're right. > Qt seems to (internally) bind it to the context event (ie. you get the rmb > instead, i was not able to add it by editing kglobalshortcutsrc) Would you report it as a bug to the Qt developers? definately not a kwin bug. I hope I found the correct product/component combination (is there a cheat sheet?). If not please assign to correct one. *** This bug has been marked as a duplicate of bug 165542 *** |