> Here is how I envision using these keys. ÂI wanted to map quick press > to GNOME3/KDE4/Unity's Activities menu and map press-and-hold to > script that rotates screen. ÂI like the repeating of rotates but I > didn't really want a rotate to also force a pop up of the activities > menu. Makes sense. >> >>> And back to the question of KEY_HOME -- that's not really what you want, >>> is it? As in "move cursor to start of line"? >> >> Ho .. right, that's what mean KEY_HOME :/. So no, I don't want that... >> What about: >> - KEY_CYCLEWINDOWS >> - KEY_COMPUTER >> - KEY_HOMEPAGE >> - KEY_DASHBOARD >> >> I think KEY_HOMEPAGE is the best choice. > > I've only had limited time to look more. ÂSo far, I found under udev a > toshiba tablet that maps what is probably a rotate button to > KEY_DIRECTION so thats one option for it instead of KEY_PROG2. ÂI > couldn't find anybody using that though. > > I see in /usr/share/X11/symbols/inet: > >  Âkey <I162>  {   Â[ XF86RotateWindows   ]    }; > > and in /usr/share/X11/xkb/symbols/evdev: > > xkb/keycodes/evdev:   <I162> = 162;  // #define KEY_CYCLEWINDOWS    Â154 > > Looks like KEY_CYCLEWINDOWS is already hooked up to > gnome-settings-daemon to auto-rotate screen? XF86RotateWindows is probably more "alt-tab" than "rotate screen". > I ran into total dead end for finding a pre-existing example of home > button usage. ÂI'm really surprised we do not yet have a KEY_LAUNCHER > or similar because so many tablet PCs/smartphones/pads do have a > button with this specific concept of "bring up your icon based > application launcher". KEY_LAUNCHER sounds like "Alt-F2" (that means krunner on KDE). The advantage over KEY_HOMEPAGE is that it would work even when a browser have the focus. > - KEY_MENU > - KEY_EXIT (smartphones sometime mean this) > - KEY_PROG3 (basically all that Windows is doing) > - KEY_LAUNCHER (why not be the first to finally create it!) > > I vote for either KEY_PROG3 or KEY_HOMEPAGE for at least short term. So now, I vote (in order): - KEY_LAUNCHER - KEY_DASHBOARD - KEY_PROG3 With this behavior (I'll use KEY_LAUCHER and KEY_PROG2) - On press, do nothing - On release, emit KEY_LAUNCHER if KEY_PROG2 wasn't emited - On press, emit only one KEY_PROG2 (I'd like to emit repeated KEY_PROG2, but I understand that it makes things harder for userspace). -- Corentin Chary http://xf.iksaif.net -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html