grail.git/include, branch master

Update copyright information

2011-04-28T16:43:16+00:00

The license information was always right, but the copyright information for this particular project was never quite right. Corrected with this patch. No functional changes. Signed-off-by: Henrik Rydberg

Introduce gesture frames

2011-04-28T16:42:33+00:00

This patch extends the API with parallel new/delete functions, aiming to eventually replace the open/close function. The new functions give access to the grail gesture frames, containing gestural transform information. This information is useful in its own right, and will eventually replace the internal recognizer. Signed-off-by: Henrik Rydberg

Expose utouch-frame through grail API

2011-04-28T14:58:51+00:00

Start a gentle API change by exposing utouch-frame through grail, and deprecating the grail_contact struct. Old programs compile and run fine. To only use the new api, compile with -DGRAIL_NO_LEGACY_API. Signed-off-by: Henrik Rydberg

Use visibility macros instead of symbol map

2011-04-28T13:19:03+00:00

Signed-off-by: Jussi Pakkanen Signed-off-by: Henrik Rydberg

Make headers work with C++

2011-04-28T13:19:03+00:00

Signed-off-by: Jussi Pakkanen Signed-off-by: Henrik Rydberg

Introduce touch gesture events

2011-03-28T20:02:11+00:00

Touch gesture events follow the same logic as drags, except they cannot be held back but are emitted immediately. Signed-off-by: Henrik Rydberg

Replace touch logic with utouch frame engine

2011-01-02T11:39:07+00:00

The original grail uses an internal touch framework and exports some touch information as extended attributes to gesture events. This was never quite the intention, but rather to expose gestures and touches on a similar footing, such that grail can be input agnostic. This patch starts off by replacing the internal touch framework with the utouch-frame engine. 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

Add contact information to the property list

2010-08-19T20:15:55+00:00

Add the five first contacts to the property list, and unify the handling of all gesture types in this regard. To avoid duplication, move the scaling of properties closer to the gesture recognizer. Move all gesture event handling code to grail-event.c, simplifying the structure somewhat. Signed-off-by: Henrik Rydberg

Crank up the maximum number of properties

2010-08-19T20:11:38+00:00

To prepare for the (for maverick only) addition of individual contact information via the properties array, increase the maximum number of contacts. Signed-off-by: Henrik Rydberg