MY evtest wheel scroll(s) results (was: 'possible bug with input handling')

[Rick Stockton]

On 01/-10/-28163 11:59 AM, Christopher Michael wrote:
> On 12/08/11 10:14, Tiago Vignatti wrote:
>> Hi, sorry for late reply.
>>
>> On 11/29/2011 08:30 PM, Christopher Michael wrote:
>>>
>>> I found an issue while working on some local code, that may be a bug in
>>> the input handling of Wayland.
>>>
>>> <<< big snip >>>
I don't know if anyone would like me to test upcoming patches, but I 
have a relatively fancy mouse, the Logitech G700. It's got 10 'genuine' 
buttons, plus a scroll wheel with Right+Left tilt.
Here are evtest results for the 4 scroll directions on my mouse, run 
into a KDE "Konsole".

(That's KDE/Kwin on top of Qt on top of X11, no Wayland compositor... 
but if we're looking at evtest command-line results, then the X11 and 
higher layers don't matter at all. (Or I'm ***badly*** confused about 
the relationship between evdev module, evtest (which I understand to be 
testing at the kernel module level, before the X11 Driver ever gets a 
chance to "mess with" the data. ;) BTW, I'm running the mouse in 
wireless mode. The Logitech USB receiver advertises the capability of 
presenting all 16 button numbers in the kernel 'input.h' range for 
"mouse buttons", but my mouse, with only only 10 "buttons", will NOT 
generate all of them.

Wheel-Up result, INCLUDING the pre-test listing of device properties:
****
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x46d product 0xc531 version 0x111
Input device name: "Logitech USB Receiver"
Supported events:
   Event type 0 (Sync)
   Event type 1 (Key)
     Event code 272 (LeftBtn)
     Event code 273 (RightBtn)
     Event code 274 (MiddleBtn)
     Event code 275 (SideBtn)
     Event code 276 (ExtraBtn)
     Event code 277 (ForwardBtn)
     Event code 278 (BackBtn)
     Event code 279 (TaskBtn)
     Event code 280 (?)
     Event code 281 (?)
     Event code 282 (?)
     Event code 283 (?)
     Event code 284 (?)
     Event code 285 (?)
     Event code 286 (?)
     Event code 287 (?)
   Event type 2 (Relative)
     Event code 0 (X)
     Event code 1 (Y)
     Event code 6 (HWheel)
     Event code 8 (Wheel)
   Event type 4 (Misc)
     Event code 4 (ScanCode)
Testing ... (interrupt to exit)
Event: time 1323467918.211785, type 2 (Relative), code 8 (Wheel), value 
1 <-- Wheel-Up was here.
Event: time 1323467918.211797, -------------- Report Sync ------------
Event: time 1323467920.147785, type 2 (Relative), code 8 (Wheel), value 
1 <-- And repeated here.
Event: time 1323467920.147795, -------------- Report Sync ------------

Wheel-Down result, EXCLUDING the pre-test listing of properties:
****
Event: time 1323467939.937783, type 2 (Relative), code 8 (Wheel), value -1
Event: time 1323467939.937793, -------------- Report Sync ------------
Event: time 1323467940.989783, type 2 (Relative), code 8 (Wheel), value -1
Event: time 1323467940.989791, -------------- Report Sync ------------

Tilt-Left result, EXCLUDING the pre-test listing of properties:
****
Event: time 1323467872.943781, type 2 (Relative), code 6 (HWheel), value -1
Event: time 1323467872.943788, -------------- Report Sync ------------
Event: time 1323467874.695782, type 2 (Relative), code 6 (HWheel), value -1
Event: time 1323467874.695789, -------------- Report Sync ------------

Tilt-Right result, EXCLUDING the pre-test listing of properties:
****
Event: time 1323467896.165783, type 2 (Relative), code 6 (HWheel), value 1
Event: time 1323467896.165791, -------------- Report Sync ------------
Event: time 1323467897.109781, type 2 (Relative), code 6 (HWheel), value 1
Event: time 1323467897.109788, -------------- Report Sync ------------

This is what I expected to see, although I have no idea what the "Misc 
-> ScanCode" event might represent. Again, this is primarily to 
volunteer my large collection of mice, my Attack-3 Joystick (it's evdev 
compatible, not a synaptics-only device), and general use Desktop for 
testing the future input API.