I see. So you didn't touch tablet during that whole log? Those jumps (firmware bug?) will be hard to deal with since it was more then 10 consecutive.
You might get lucky and can add some masking logic. maybe something like: if (!coord.proximity || !(coord.tip || coord.eraser)) coord.pressure = 0; I've no real idea really what tip/eraser/side are meant to convey in ISDV4's packets but you get the basic idea I bet. See if enough information is in packet to know when pressure values are invalid and zero out. Chris On Thu, Jan 13, 2011 at 2:29 PM, AndrewP <[email protected]> wrote: > > > http://dpaste.org/L5j1/ as you can see my Threshold value is already set to > 150 > anyway I have about half of pressure levels range. So "jumping" values is my > initial problem. > > On Thu, Jan 13, 2011 at 20:22, Chris Bagwell <[email protected]> wrote: >> >> Maybe its a "Thresold" parameter error. Can you try playing with >> different values and see if it improves. man page says its a ratio of >> MaxPressure but really its hard coded to 75. >> >> Your "p" values (raw pressure from hardware) was either zero or jumped >> to value higher then 6. Most time it was MUCH higher then 7. >> >> My rough math says currently any pressure over 4 on your hardware >> would be detected as a click. >> >> I think you'll want a minimum value of 112 because of: >> MaxPressure=127 so 127*3/50=7 so 7*(2048/127)=112. >> >> Chris >> >> On Thu, Jan 13, 2011 at 1:53 PM, AndrewP <[email protected]> wrote: >> > it was more tricky, I've compiled it without debug flag. recompiled the >> > driver and all went well with xsetwacom >> > I got massive log from Xorg. Feared to drop something important so >> > posted >> > most of it http://dpaste.org/4SO3/ >> > In log reproduced false clicks(without touching), and simple strokes >> > with >> > tip and eraser. >> > >> > >> > On Thu, Jan 13, 2011 at 19:38, Chris Bagwell <[email protected]> >> > wrote: >> >> >> >> It may help if you enable debug mode and view your /var/log/Xorg.0.log >> >> file for clues. >> >> >> >> xinput set-prop "name of stylus device" "Wacom Debug Levels" 10 10 >> >> >> >> Try testing your tablet and then the log file will contain a few >> >> references of "p=value" and we can see what pressure your hardware is >> >> reporting; before its transformed anyways. I think after its >> >> transformed it will be in form "z=value". >> >> >> >> If you can't set that property then it means you have an older version >> >> of xf86-input-wacom installed which doesn't default to compiling in >> >> debug support. I suggest upgrading in that case to latest git version >> >> (.10-10 has filter bug) and try again. >> >> >> >> Also, sending the output of "xsetwacom get stylus all" may provide >> >> clues as well. >> >> >> >> Chris >> >> >> >> On Thu, Jan 13, 2011 at 1:25 PM, AndrewP <[email protected]> wrote: >> >> > Is it necessary for you to get to another system? Can't we gather any >> >> > more >> >> > information from mine? >> >> > Isn't it possible to sniff some from Windows? >> >> > >> >> > When I've looked through my Intous3 params on desktop, I noticed >> >> > some >> >> > parameter named "CursorProx". It is unavailable for my Tablet PC, >> >> > despite, >> >> > concept of cursor proximity caught my attention. I experience false >> >> > "pressure" even when I don't touch screen with pen tip, can it be >> >> > related? >> >> > >> >> > But I have very limited pressure level range indicated in xinput, so >> >> > it >> >> > as >> >> > well could be nothing to do with that. >> >> > >> >> > Anyway is there anything else I could do? I guess you can understand >> >> > my >> >> > impatience on this matter =) >> >> > >> >> > >> >> > On Mon, Jan 10, 2011 at 22:11, Ping Cheng <[email protected]> >> >> > wrote: >> >> >> >> >> >> On Mon, Jan 10, 2011 at 10:52 AM, AndrewP <[email protected]> >> >> >> wrote: >> >> >> > Happened to boot to Win7 again, and must notice it is wholly >> >> >> > different >> >> >> > experience there. >> >> >> >> >> >> I know. They meant to be different since we counted on you, the >> >> >> users, >> >> >> as well on Linux ;). >> >> >> >> >> >> > Any luck with our driver? >> >> >> >> >> >> Not yet. No time to get to another system soon... >> >> >> >> >> >> Ping >> >> > >> >> > >> >> > >> >> > >> >> > ------------------------------------------------------------------------------ >> >> > Protect Your Site and Customers from Malware Attacks >> >> > Learn about various malware tactics and how to avoid them. Understand >> >> > malware threats, the impact they can have on your business, and how >> >> > you >> >> > can protect your company and customers by using code signing. >> >> > http://p.sf.net/sfu/oracle-sfdevnl >> >> > _______________________________________________ >> >> > Linuxwacom-devel mailing list >> >> > [email protected] >> >> > https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel >> >> > >> >> > >> > >> > > > > > ------------------------------------------------------------------------------ > Protect Your Site and Customers from Malware Attacks > Learn about various malware tactics and how to avoid them. Understand > malware threats, the impact they can have on your business, and how you > can protect your company and customers by using code signing. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Linuxwacom-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel > > ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
