On Fri, Mar 05, 2010 at 08:33:56AM -0600, Chris Bagwell wrote: > On Fri, Mar 5, 2010 at 6:29 AM, Peter Hutterer <peter.hutte...@who-t.net> > wrote: > > On Fri, Mar 05, 2010 at 01:02:18AM -0800, Bryan Hundven wrote: > > > >> EVENT type 17 > >> device: 2 > >> detail: 0 > >> valuators: > >> 0: 3078.00 (3078.00) > >> 1: 1548.00 (1548.00) > >> 2: 0.00 (0.00) > >> 3: 0.00 (0.00) > >> 4: 0.00 (0.00) > >> 5: 0.00 (0.00) > > > > these suggest that there's no accel applied to the tablet, so it's somewhere > > in the driver code. not sure what yet, I need to dig into this. I thought > > just purging the in-driver accel code was enough but maybe that's not the > > case. thanks for providing all the info. > > > > > There is a step that may help. Turn on debug output and this will > dump some useful info to your Xorg.log file. After reproducing your > problems, you can upload the logs to the bug report. Try to include > some timestamp information so we can tell where each test was. > > Replace "11" with any of the wacom ID's. > > xinput set-prop 11 "Wacom Debug Levels" 10 10
just ftr, it's often better to use the full device name, especially if you're giving others instructions on lists. xinput --set-prop "Wacom Intuos4 6x9 eraser" "Wacom Debug Levels" 10 10 for example, will set the property for the eraser. Unless you plug in two wacom tablets, this name will stay the same so you don't have to check the ID after each unplug. (also, this way you can use Ctrl+R :) Cheers, Peter > Look for output when wcmEvent() is called and see if you see if a wild > swing in X/Y values occurs around time you see un-expected behavior. > > You've also mentioned about eraser getting treated like pen, etc. > This debug will help show some information related to that. > > I see some cleanup logic that I don't understand that fixes when it > thinks its an eraser but really is a stylus... but I do not see the > opposite cleanup to fix stylus that are really erasers (see > isdv4Parse(), around line 513). Perhaps having the device, you > understand the comment in code better about "sideswitch". ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
