diff options
| author | Peter Hutterer <peter@cs.unisa.edu.au> | 2008-05-23 11:51:53 +0930 |
|---|---|---|
| committer | Peter Hutterer <peter@cs.unisa.edu.au> | 2008-05-23 12:01:37 +0930 |
| commit | 6c9e9f8a40e20fb1761440acd2755f5fd31f4d44 (patch) | |
| tree | 51093ef132aceaef19cfe43df0d42f9124b2157e /Xi | |
| parent | fb146cbb0f28e4e480e5d16d61476ac46b5d00ce (diff) | |
input: instead of lastx/y, use a last.valuators[] array on the device.
During GetPointerEvents (and others), we need to access the last coordinates
posted for this device from the driver (not as posted to the client!). Lastx/y
is ok if we only have two axes, but with more complex devices we also need to
transition between all other axes.
ABI break, recompile your input drivers.
Diffstat (limited to 'Xi')
| -rw-r--r-- | Xi/warpdevp.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Xi/warpdevp.c b/Xi/warpdevp.c index 3720441d9..502cab402 100644 --- a/Xi/warpdevp.c +++ b/Xi/warpdevp.c @@ -166,8 +166,8 @@ ProcXWarpDevicePointer(ClientPtr client) } /* if we don't update the device, we get a jump next time it moves */ - pDev->lastx = x; - pDev->lasty = x; + pDev->last.valuators[0] = x; + pDev->last.valuators[1] = x; miPointerUpdateSprite(pDev); /* FIXME: XWarpPointer is supposed to generate an event. It doesn't do it |