I was reviewing pressure code and thinking about pressure issue reported on linuxwacom-discuss. I noticed we do these steps (thanks to recent refactor, its easy to copy&paste now :-) ):
filtered.pressure = normalizePressure(priv, &filtered); filtered.buttons = setPressureButton(priv, &filtered); transPressureCurve(priv,&filtered); I'm thinking order of transPressureCurve() and setPressureButton() should be swapped. Any reason its in current order? Lets say your pressure has an initial jump from 0 pressure to 30-ish (nothing in between) and the HW reported pressure curve is steep until you get to 30% pressure. Those #'s are exaggerated high but I found a PDF on Wacom web page that shows pressure curve is roughly that shape. Right now, you'd have to play with both PressCurve and Threshold to get comfortable usage. If we swapped those two function calls then probably you can use only PressCurve to ignore pressure < 30 and smooth out that initial steep incline. I suspect if user wants a "harder" pressure curve then they still want Thresold=27 to work relative to 27 on the pressure curve. Thoughts? Chris ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
