User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20060601 Firefox/2.0 (Ubuntu-edgy)
Even if a key does not correspond to some keysym, "Keyboard Preferences -> Shortcuts" should accept that key. This avoids requiring the user to mess up the system with xmodkeys definitions and loading them upon startup.
GNOME does this by giving a name to the key e.g. "0xae" to denote the keycode received.
Steps to Reproduce:
What version of gtk+ are you using?
Edgy? it's gtk+-2.10.x then. So it should work.
Ah, sorry. Multimedia keys (thought of windows key as modifier, an old story).
The thing is, the shortcuts editor deals with keycodes. As long as keyvodes are defined, t works.
If you want to have more keycodes defined by default, either ask the distribution to fix that or X.org to add more keyboard types.
Maybe we should try to use keycode and not just keysyms. That would be less portable accross the platforms (for example, you you log from another workstation, the keycode may differ)
> Maybe we should try to use keycode and not just keysyms.
> That would be less portable accross the platforms (for example,
> you you log from another workstation, the keycode may differ)
guess I would not be using the same keyboard from another workstation anyway. Therefore the unportability is acceptable as long as it is bounded to only keys which have no keysyms.
Implemented in trunk. This doesn't work with modifiers though, because of the way gdk decompose modifiers and keys.
Tested and works very well. Please consider backporting to 4.4 branch. Thanks!
But why do you use aumix instead of the more popular amixer?
(In reply to comment #8)
> But why do you use aumix instead of the more popular amixer?
amixer is Linux-only. We run on a lot more than just Linux. In that sense, amixer is not more popular than aumix. It's just a default; users can change it to suit to taste. And, most importantly, Linux distribution packagers can provide a different default keytheme to suit the applications available on their distro.