grail.git, branch v1.0.13

grail v1.0.13

2010-09-10T12:06:15+00:00

Allow slow tapping

2010-09-10T12:06:12+00:00

For the benefit of hardware that cannot accurately meet the desirable response times, allow for tapping times up to 300 ms. Signed-off-by: Henrik Rydberg

Inhibit taps immediately after a finger is lifted

2010-09-10T12:06:10+00:00

The intentional tap starts with a finger in the air. This patch treats the sequence up-down-up as unintentional, unless performed with a single finger. Fixes the problem with accidental taps during multi-finger gestures. Signed-off-by: Henrik Rydberg

Only emit abs events when motion is active

2010-09-10T10:28:17+00:00

This bug was hidden behind the motion inhibit during tapping, but resurfaced when tapping from resting finger was introduced. With this patch, pointer movement is inhibited also when lifting fingers from the surface. Ideally, tapping should be treated as a transient event, which would allow zero pointer event also _before_ the tap, but presently unity seems to depend on the initial pointer movement as a touch-down event. Signed-off-by: Henrik Rydberg

Cancel tapping also on zoom events

2010-09-09T19:05:11+00:00

The current code cancels tapping when dragging is active. This patch adds zooming to the set, to inhibit tapping also when a perfect zoom without dragging is performed. Reported-by: Chase Douglas Signed-off-by: Henrik Rydberg

Discard tapping even when there are zero events between down and up

2010-09-09T19:05:11+00:00

The current logic assumes there will be at least one frame with between touch up and touch down or the tap will not be properly timed out. Fixed with this patch. Reported-by: Chase Douglas Signed-off-by: Henrik Rydberg

Support legacy devices

2010-09-09T08:17:09+00:00

Simulate MT touch events for legacy devices that support the DOUBLETAP, TRIPLETAP and QUADTAP events. This allows multi-finger tap and drag gestures to be emitted, providing a basic level of MT functionality for legacy devices. Signed-off-by: Henrik Rydberg

Make sure contact area is always defined

2010-09-09T08:14:26+00:00

Some devices do not always send touch_minor after touch_major has been set. According to the MT protocol, this case should be treated as if minor is equal to major. This patch makes sure touch_minor is never zero when touch_major is set. Signed-off-by: Henrik Rydberg

grail v1.0.12

2010-09-01T19:18:09+00:00

Do not compute velocity until enough data is available

2010-09-01T19:18:07+00:00

The first few ticks since a configuration change are not really suited for velocity computation, so move the speed computation over to the periodic sampling point. Signed-off-by: Henrik Rydberg