lp:~chasedouglas/grail/trunk.tapping

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

83. By Chase Douglas on 2010-09-09

grail v1.0.13

82. By Chase Douglas on 2010-09-09

Check time elapsed before emitting touch

Multiple fingers may be down and not have moved for a period of time.
When a finger is lifted, a tap gesture may be emitted. This change
ensures that the length of time elapsed for the tap is within the tap
range before emitting the tap gesture.

81. By Chase Douglas on 2010-09-09

Use total absolute motion to inhibit tapping

Currently, only focus point motion inhibits tapping. However, a pinch
motion may not move the focus point, and may be fast enough to register
as a tap. This change adds a new motion model type that aggregates the
total absolute motion. A tap is prevented from being recognized if the
total absolute motion is significant.

80. By Henrik Rydberg on 2010-09-09

Support legacy devices

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.

79. By Henrik Rydberg on 2010-09-09

Make sure contact area is always defined

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.

78. By Henrik Rydberg on 2010-09-01

grail v1.0.12

77. By Henrik Rydberg on 2010-09-01

Do not compute velocity until enough data is available

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.

76. By Henrik Rydberg on 2010-08-31

Make orientation computation more robust

The MT protocol defines the angle to be between -Pi/2 and Pi/2,
and expects the defined range to be symmetric around zero.
Make the angle computation more robust against varying definitions
in the kernel drivers.

75. By Henrik Rydberg on 2010-08-26

grail v1.0.11

74. By Henrik Rydberg on 2010-08-26

Introduce tapping from any finger configuration

The current code only emits taps from zero fingers to N fingers.
This patch introduces tapping from any prior finger configuration.
A tap is defined as an increased number of fingers followed by a
decrease within the tap timeout. A tap is reported as the maximum
number of fingers present during the tap sequence.