A sample xev output for a left Super/Windows keypress looks like:
KeyPress event, serial 27, synthetic NO, window 0xe00001, root 0x24a, subw 0x0, time 1245455660, (760,-150), root:(763,559), state 0x0, keycode 133 (keysym 0xffeb, Super_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False
I notice that my Logitech T400 (a mouse designed for Windows 8, with two middle buttons- one of which is interpreted as a left Super key) generates the same output with the exception of the "serial field." It generates "28" instead of "27."
- What is the serial field?
- Is there a way to use this to map the mouse's key to a different action than the keyboard's key (and if so, what is it)?
Context: I would like both middle buttons on the mouse to be middle click, which I have accompished with xbindkeys and mvmouse using steps similar to these. However, this leaves my keyboard's left Super key also a middle button. It would be nice to retain the keyboard's key so I can use it with my window manager (i3.)