More precisely, if I press e.g. the button marked "+", the events
KeyPress event, serial 32, synthetic NO, window 0x1a00001,
root 0x63, subw 0x0, time 1093549082, (89,131), root:(1110,155),
state 0x0, keycode 176 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 32, synthetic NO, window 0x1a00001,
root 0x63, subw 0x0, time 1093549258, (89,131), root:(1110,155),
state 0x0, keycode 176 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
are generated.
Obviously, some engineer was very smart again, because he "knew" that if someone needs a mouse, than he surely needs two buttons for volume control and two buttons to control audio player. Yes, of course I can change actions assigned to these keys, but this also changes actions assigned to appropriate keys on real keyboard. So I can make my choice. Either I will be able to change the volume by mouse and keyboard, or by none of the two. Next time, I'll buy myself a Logitech mouse :-)
Žádné komentáře:
Okomentovat