On Sun, Jun 26, 2011 at 7:24 PM, Peter Hutterer <peter.hutte...@who-t.net> wrote: > On Sat, Jun 25, 2011 at 01:05:49PM -0500, ch...@cnpbagwell.com wrote: >> From: Chris Bagwell <ch...@cnpbagwell.com> >> >> The feature never fully worked and bits have slowing been removed. >> Remove remaining in one swoop. >> >> As apart of removing logic, now store ABS_PRESSURE values in the more >> appropriate "pressure" location so that it can eventually be exposed in >> the Pressure axis that touch devices create but do not currently send. > > I do wonder how this works for ISDV4 devices where the capacity still comes > in through capacity, not pressure. We don't have separate devices here > (unlike the bamboos). Any comments? > > Otherwise, +1 for merging the two into a "pressure" setting, having Capacity > exposed is not necessary. >
Ping, do you happen to have a ISDV4 device around to comment? In patch below, I deleted the line were ISDV4 capacity was being stored in ds.capacity. To user, there will be no visible change because we ignored that variable. That means that the Pressure Axis will be fixed at zero; same as today. They would probably get a better user experience if we didn't create the pressure axis. Since the old unused Capacity property could only be set to maximum of 5 and originated for ISDV4, I suspect the hardware value maxed out at 10 or so and so not useful in practice. Chris ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
