On Sun, Dec 18, 2011 at 7:28 PM, Chris Bagwell ch...@cnpbagwell.com wrote:
Hi all,
I messed up in input-wacom 0.12.0 release. I said that it supported
2nd gen Bamboo but it did not.
Its just a few lines of code so I missed it in the noise. At the
moment I took the dtor-next snapshot, the
Adds the Cintiq 24HD (056a:00f4) to the device lists. The 24HD
has two features not found on prior tablets: three capacitive
buttons, and a second touch ring. Subsuquent patches will
address adding support for them.
Signed-off-by: Jason Gerecke killert...@gmail.com
Reviewed-by: Chris Bagwell
Touch strips as well as the first touch ring are set up to emulate
mouse wheel events by default. This patch duplicates this behavior
for the second touch ring, so that it behaves in an identical manner.
Signed-off-by: Jason Gerecke killert...@gmail.com
---
Changes from v3:
* Move after
Replaces sendWheelStripEvents and getWheelButton with several
small functions to reduce unnecessary code duplication.
As a side-effect, it is now possible for the driver to handle
simultaneous scrolls on multiple axes. Previously, getWheelButton
would go through all the axes but was limited to
This patch expands the number of valuators reported by devices to
seven. The new seventh valuator reports the raw value provided from
the kernel for the second touch ring.
Signed-off-by: Jason Gerecke killert...@gmail.com
Reviewed-by: Peter Hutterer peter.hutte...@who-t.net
Reviewed-by: Chris
This patch adds an 'abswheel2' field to the _WacomDeviceState
structure, along with corresponding 'oldWheel2' field to the
_WacomDeviceRec structure. These fields store the state of the
second touch ring on dual-ring devices such as the Cintiq 24HD.
Signed-off-by: Jason Gerecke
On Wed, Dec 21, 2011 at 7:29 AM, Ping Cheng pingli...@gmail.com wrote:
On Sun, Dec 18, 2011 at 7:28 PM, Chris Bagwell ch...@cnpbagwell.com wrote:
Hi all,
I messed up in input-wacom 0.12.0 release. I said that it supported
2nd gen Bamboo but it did not.
Its just a few lines of code so I
On Wed, Dec 21, 2011 at 03:28:54PM -0800, Jason Gerecke wrote:
Replaces sendWheelStripEvents and getWheelButton with several
small functions to reduce unnecessary code duplication.
As a side-effect, it is now possible for the driver to handle
simultaneous scrolls on multiple axes.
On Wed, Dec 21, 2011 at 03:28:57PM -0800, Jason Gerecke wrote:
Touch strips as well as the first touch ring are set up to emulate
mouse wheel events by default. This patch duplicates this behavior
for the second touch ring, so that it behaves in an identical manner.
Signed-off-by: Jason
