On Thu, Oct 18, 2012 at 7:12 PM, Thomas Jaeger thjae...@gmail.com wrote:
On 09/29/2012 07:58 PM, Jason Gerecke wrote:
@@ -419,6 +419,14 @@ static int wcmDevInit(DeviceIntPtr pWcm)
return FALSE;
}
+#if GET_ABI_MAJOR(ABI_XINPUT_VERSION) = 16
+ if
On 09/29/2012 07:58 PM, Jason Gerecke wrote:
@@ -419,6 +419,14 @@ static int wcmDevInit(DeviceIntPtr pWcm)
return FALSE;
}
+#if GET_ABI_MAJOR(ABI_XINPUT_VERSION) = 16
+ if (!InitTouchClassDeviceStruct(pInfo-dev, 0, XIDependentTouch, 2)) {
+
On Sat, Sep 29, 2012 at 7:12 PM, Thomas Jaeger thjae...@gmail.com wrote:
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
On 09/30/2012 07:47 PM, Jason Gerecke wrote:
Could you explain this in a little more detail? My tests with both
indirect and direct touch devices haven't revealed any regression like
this. I admittedly haven't tested the absolute case as thoroughly as
the relative one (due to a lack of
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
