~oif-team/grail/one-touch-indirect : changes

~oif-team/grail/one-touch-indirect » Changes from revision 112

From Revision 112 to 93

Rev	Summary	Authors	Tags	Date
112	Don't generate one touch gestures for indirect devices Don't generate one touch gestures for indirect devices	Chase Douglas		13 years ago
111	Don't treat key events differently anymore Don't treat key events differently anymore Left over from grail pointer emulation.	Chase Douglas		13 years ago
110	Add in time boundaries for recognition Add in time boundaries for recognition 50 ms: Minimum time waiting for touch configuration to settle before flushing touch events to X. We don't want a two finger gesture triggering X events for the first finger before the second finger lands. 200 ms: Maximum time for touches to begin a gesture. If no gesture is found within this time period, the events are flushed to X. If after 50 ms there are no possible gestures for the number of active touches, the events are immediately flushed to X. If events are flushed to X, no more gesture recognition is possible until all touches are lifted. Likewise, if any gesture is recognized, no events may be flushed to X until all touches are lifted.	Chase Douglas		13 years ago
109	Remove pointer emulation, X will handle it Remove pointer emulation, X will handle it	Chase Douglas		13 years ago
108	Small compilation warning fixes Small compilation warning fixes Found by using -Wall -Werror	Chase Douglas		13 years ago
107	Bump to v1.0.18 Bump to v1.0.18 The grail symbols are intact and abi compatible, whereas the remaining symbols, which should not really be present, have all been removed. Since the remaining symbols represent the actual official API, this is not considered an ABI breakage.	Henrik Rydberg	v1.0.18	13 years ago
106	Only export the intended grail symbols Only export the intended grail symbols In the making of grail1, the intention was never that the gin, gru and touch symbols be exported. Rectify this by adding an explicit symbols file used during linking.	Henrik Rydberg		13 years ago
105	Replace touch logic with utouch frame engine Replace touch logic with utouch frame engine 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.	Henrik Rydberg		13 years ago
104	Prepare for queued event handling Prepare for queued event handling The current grail operates via callbacks. In order to make grail work as a pipe, where input and output can be controlled externally, add the missing event queue for gestures, and align the code to simplify a switch.	Henrik Rydberg		13 years ago
103	Move test program to tools directory Move test program to tools directory The current test programs are tools rather than automatic tests. To conform better to the the usage of "make check", move the current tools over the appropriate directory. Also drop the grail-touch program, as it will be replaced by the utouch-frame package.	Henrik Rydberg		13 years ago
102	grail v1.0.17 grail v1.0.17	Henrik Rydberg	v1.0.17	13 years ago
101	Use a unified pointer emulation model Use a unified pointer emulation model The existing kernel MT devices together use a handful of different pointer emulation strategies, each with its own subtlety. This creates a problem for grail, which needs to rebuild pointer emulation during gesture recognition; relying on the correct pointer information to be available at the right time becomes almost impossible. This patch implements a common pointer emulation model for grail, following a strategy recently discussed on LKML. This resolves the problems stemming from different emulation strategies, and results in a common pointer emulation experience for all devices.	Henrik Rydberg		13 years ago
100	grail v1.0.16 grail v1.0.16	Henrik Rydberg	v1.0.16	13 years ago
99	Report touch down on one-finger entry (LP: #667802) Report touch down on one-finger entry (LP: #667802) The current code mistakenly set the pointer logic based on the single variable, which is false at the entry to one-finger mode, but true immediately afterwards. This leads to grail sometimes failing to emit the proper emulation sequence, resulting in a missed touch in X. This patch corrects the logic such that the pointer is based directly on one-finger mode, thereby solving the problem.	Henrik Rydberg		13 years ago
98	grail v1.0.15 grail v1.0.15	Henrik Rydberg	v1.0.15	13 years ago
97	Only support pure absolute devices at this time Only support pure absolute devices at this time There are some hybrid relative/absolute devices out there, like the magic mouse, for which special behavior, outside the current scope of grail, is expected. This patch disables grail for those devices.	Henrik Rydberg		13 years ago
96	grail v1.0.14 grail v1.0.14	Henrik Rydberg	v1.0.14	13 years ago
95	Show all information for pass-through events Show all information for pass-through events In grail-gesture, the timing information is missing. Remedied with this patch.	Henrik Rydberg		13 years ago
94	Add tap state to the tapping model Add tap state to the tapping model Add the ability to read off the tap state in the tapping model. Useful for emulation i lieu of tapping gestures.	Henrik Rydberg		13 years ago
93	Add tap emulation Add tap emulation Touchscreens always emit a button event when touching the screen. Trackpads, however, are considered hovering while touching the pad, and instead uses taps to emits button events, which is traditionally implemented elsewhere, and thus leaves a functionality discrepancy. This patch adds tap emulation to grail, utilizing gesture engine.	Henrik Rydberg		13 years ago

Older »