The X server has had multi-touch support for a while now, and most newer
wacom devices seem to have some limited multi-touch capability, so it
would be nice to take advantage of that. So far there is no support for
multi-touch in the xf86-input-wacom driver, although the kernel driver
does
This set of patches adds multitouch support to the driver. The new
API made available in XI2.2 is used to report the location of all
contacts, allowing applications to work with the touch points themselves.
This is added as a new gesture mode, taking over whenever in-driver
gestures have been
Code that deals with touch points shouldn't care which channel an
event is occuring in; it should be more concerned with the finger
that caused it. At the moment these are the same things (first
finger is always in channel zero), but this will soon change.
Signed-off-by: Jason Gerecke
Instead of keeping around 'channel_changed', 'mt_channel_changed',
and 'btn_channel_changed', just add a flag to the WacomChannel
itself that can be set whenever something changes.
Signed-off-by: Jason Gerecke killert...@gmail.com
---
src/wcmUSB.c| 89
At the moment, disabling gestures disables *all* gestures. That includes
the core tap to click gesture (and slightly-less-core tap and hold to
drag). This patch changes the behavior of the driver to always allow
single finger gestures, even if gestures have been disabled. This makes
using the
Instead of having different per-protocol cases, just obtain serial
numbers equivelent to those you'd get from Protocol 5 and then
use that serial to find a channel dynamically.
Signed-off-by: Jason Gerecke killert...@gmail.com
---
src/wcmUSB.c | 178
Tweaks the usbInitToolType function to be always useful. This is
needed so that we can use it to get the tool type for all event
frames, allowing us to properly fill in the tool type for devices
that we otherwise don't figure out until later on (which causes
problems with the proper operation of
Adds a new MULTITOUCH gesture mode that will redirect all in-contact
touches through the new multitouch code available in XI2.2 (ABI = 16).
MULTITOUCH mode will only be entered when in-driver gestures have been
disabled and at least two fingers are present. The driver will remain
in this mode
Right now the driver assumes that the first touch will always
be in channel 0, and the second touch (if present) is in
channel 1. This patch adds a new function to scan the channel
list for appropriate contacts, and uses it instead of the
hard-coded index accesses.
Signed-off-by: Jason Gerecke
Instead of divining this information from the stored private data,
take them as arguments. This gives us more flexibility in finding
channels for sub-tools (e.g. individual fingers).
Signed-off-by: Jason Gerecke killert...@gmail.com
---
src/wcmUSB.c | 18 --
1 file changed, 8
Now that the touch code doesn't look in statically-defined
channels and usbChooseChannel is capable of locating channel
numbers for arbitrary tool type/serial combinations, we can
use the latter to track an aribrary number of touches without
fear of stepping on the toes of another channel.
On Sat, Sep 29, 2012 at 3:19 PM, Thomas Jaeger thjae...@gmail.com wrote:
The X server has had multi-touch support for a while now, and most newer
wacom devices seem to have some limited multi-touch capability, so it
would be nice to take advantage of that. So far there is no support for
On 09/29/2012 07:58 PM, Jason Gerecke wrote:
Adds a new MULTITOUCH gesture mode that will redirect all in-contact
touches through the new multitouch code available in XI2.2 (ABI = 16).
MULTITOUCH mode will only be entered when in-driver gestures have been
disabled and at least two fingers are
On 09/29/2012 09:37 PM, Thomas Jaeger wrote:
On 09/29/2012 07:58 PM, Jason Gerecke wrote:
Adds a new MULTITOUCH gesture mode that will redirect all in-contact
touches through the new multitouch code available in XI2.2 (ABI = 16).
MULTITOUCH mode will only be entered when in-driver gestures
On 09/29/2012 07:58 PM, Jason Gerecke wrote:
For the moment, all touches are sent as XIDependentTouch. Direct touch
devices such as tablet PCs and Cintiqs are not an exception. This may
be changed in the future once frameworks are better equipped to handle
direct input touches.
For users that
15 matches
Mail list logo