Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
GNOME Shell, extensions, and control
Posted Jun 23, 2011 14:56 UTC (Thu) by mjg59 (subscriber, #23239)
Posted Jun 23, 2011 18:21 UTC (Thu) by nix (subscriber, #2304)
More generally, the whole area of scancodes is a confusing and ill-thought-out mess replete with historical horrors, best avoided. At this point I have no idea *where* GNOME Shell gets its codes from, and no clue what key is used for this feature at all, only that the key above tab doesn't generate any of the codes you've suggested (not scancodes, nor X keycodes) on any keyboard I have access to, conventional or not. I'd have to look at the code... (I'm fairly sure it's not actually using scancodes, though, because that would require raw access. Are you talking about X keycodes? They're quite different.)
Why not just make this stuff an option so people can set a key and know what it is without having to go through all this trouble? Or use a keysym like every single other X app since the dawn of time?
Posted Jun 23, 2011 18:27 UTC (Thu) by mjg59 (subscriber, #23239)
Posted Jun 23, 2011 21:26 UTC (Thu) by nix (subscriber, #2304)
If the default can be overridden, then I have no complaints: most users *are* indeed using evdev (even users of obscure keyboards): that I am not is entirely my own damn fault.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds