On Thursday, August 26, 2010, Chris Bagwell <[email protected]> wrote: > The output from kernel looks reasonable to me (note: I do not have > such a tablet to compare to). > > I notice that on initial touch the values jump a little bit. I don't > see any averaging logic to smooth that out in kernel or > xf86-input-wacom which is a little surprising...but thats a different > topic. > > I did look further back in stack of xf86-input-wacom from my previous > mention and I see a secondary level were it assumes a value of zero > only when scroll ring is out-of-proxity (in sendCommonEvent()). > > 759 v5 = ds->abswheel; > 871 if (v3 || v4 || v5 || buttons || ds->relwheel) > 872 { > 873 sendCommonEvents(pInfo, ds, x, y, z, v3, v4, v5); > > So this looks to me like a X side bug that is samewhat new when their > values were normalized.
Sorry it takes so long to get back to you. I've reproduced and fixed the issue. It is not related to normalization. We did not normalize v3 and v4 (we did it for stylus on v5). EH, if you have time, please test it. Thank you. Ping > Hopefully Ping or Peter can offer a proper fix. > > Chris > > On Thu, Aug 26, 2010 at 12:09 PM, holzminister > <[email protected]> wrote: >> No problem, here comes the next try: >> >> Scrolling down: >> >> Event: time 1282842084.764066, type 3 (Absolute), code 8 (Wheel), value 26 >> Event: time 1282842084.764073, type 4 (Misc), code 0 (Serial), value -1 >> Event: time 1282842084.764076, -------------- Report Sync ------------ >> Event: time 1282842084.812060, type 3 (Absolute), code 8 (Wheel), value 27 >> Event: time 1282842084.812066, type 4 (Misc), code 0 (Serial), value -1 >> Event: time 1282842084.812068, -------------- Report Sync ------------ >> Event: time 1282842084.840061, type 3 (Absolute), code 8 (Wheel), value 26 >> Event: time 1282842084.840067, type 4 (Misc), code 0 (Serial), value -1 >> Event: time 1282842084.840070, -------------- Report Sync ------------ >> Event: time 1282842084.864058, type 3 (Absolute), code 8 (Wheel), value 27 >> Event: time 1282842084.864063, type 4 (Misc), code 0 (Serial), value -1 >> Event: time 1282842084.864065, -------------- Report Sync ------------ >> Event: time 1282842085.388054, type 3 (Absolute), code 8 (Wheel), value 28 >> Event: time 1282842085.388060, type 4 (Misc), code 0 (Serial), value -1 >> Event: time 1282842085.388064, -------------- Report Sync ------------ >> Event: time 1282842085.488054, type 3 (Absolute), code 8 (Wheel), value 29 >> Event: time 1282842085.488060, type 4 (Misc), code 0 (Serial), value -1 >> Event: time 1282842085.488064, -------------- Report Sync ------------ >> Event: time 1282842086.064042, type 3 (Absolute), code 8 (Wheel), value 0 >> Event: time 1282842086.064049, type 1 (Key), code 325 (ToolFinger), value 0 >> Event: time 1282842086.064051, type 3 (Absolute), code 40 (Misc), value 0 >> Event: time 1282842086.064053, type 4 (Misc), code 0 (Serial), value -1 >> Event: time 1282842086.064056, -------------- Report Sync ------------ >> >> >> Something interesting to see? :) >> >> >> Best regards, >> EH >> >> >> >> >> Am Thu, 26 Aug 2010 11:04:30 -0500 >> schrieb Chris Bagwell <[email protected]>: >> >>> Opps, we forgot to mention important fact. You need to switch your >>> console away from X for evtest to be able to see the events. >>> >>> When its working right, you'll see printing to the screen as you use >>> tablet. >>> >>> Chris >>> >>> On Thu, Aug 26, 2010 at 11:02 AM, holzminister >>> <[email protected]> wrote: >>> > Hi! >>> > >>> > I don't know how wrong output should look like, so I I have to give >>> > you the full one: >>> > >>> > ##### >>> > Input driver version is 1.0.0 >>> > Input device ID: bus 0x3 vendor 0x56a product 0xb9 version 0x104 >>> > Input device name: "Wacom Intuos4 6x9" >>> > Supported events: >>> > Event type 0 (Sync) >>> > Event type 1 (Key) >>> > Event code 256 (Btn0) >>> > Event code 257 (Btn1) >>> > Event code 258 (Btn2) >>> > Event code 259 (Btn3) >>> > Event code 260 (Btn4) >>> > Event code 261 (Btn5) >>> > Event code 262 (Btn6) >>> > Event code 263 (Btn7) >>> > Event code 264 (Btn8) >>> > Event code 272 (LeftBtn) >>> > Event code 273 (RightBtn) >>> > Event code 274 (MiddleBtn) >>> > Event code 275 (SideBtn) >>> > Event code 276 (ExtraBtn) >>> > Event code 320 (ToolPen) >>> > Event code 321 (ToolRubber) >>> > Event code 322 (ToolBrush) >>> > Event code 323 (ToolPencil) >>> > Event code 324 (ToolAirbrush) >>> > Event code 325 (ToolFinger) >>> > Event code 326 (ToolMouse) >>> > Event code 327 (ToolLens) >>> > Event code 330 (Touch) >>> > Event code 331 (Stylus) >>> > Event code 332 (Stylus2) >>> > Event type 2 (Relative) >> ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
