From f0aba58c91933a4702a7cc74f7daf4192868f570 Mon Sep 17 00:00:00 2001 From: Henrik Rydberg Date: Thu, 30 Dec 2010 17:58:01 +0100 Subject: Initial load of utouch-frame Compiles and runs on mtdev. ABI proof. Signed-off-by: Henrik Rydberg --- docs/event-semantics.txt | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 docs/event-semantics.txt (limited to 'docs') diff --git a/docs/event-semantics.txt b/docs/event-semantics.txt new file mode 100644 index 0000000..87afe4e --- /dev/null +++ b/docs/event-semantics.txt @@ -0,0 +1,31 @@ +FRAME + +The touch frame, consisting of a set of simultaneous contacts. + +CONTACT + +The current MT contact configuration. Changes whenever an id changes. + +TOUCH + +The current touch configuration. Changes whenever the number of contacts +changes. A touch frame is well-defined a time T after the last +configuration change. This allows for simultaneous touches being +handled. It also allows for a very quick change of one finger to +another. Such an action changes the CONTACT state, but it does not change +the TOUCH state. + +DRAG/PINCH/ROTATE + +A transformation based on the touch frame. + +GESTURES + +Two creation points may be grouped if they are close in space-time, and +they are always close within the same controlling entity. There can be only +one controlling entity per point, and that decision is made upon +creation. The window manager is a controlling entity. Ambiguities can occur +between close points, and are resolved either by state rule or by +priority. Relaxing the time closeness criteria has no effect within a +controlling entity, but creates a larger set of ambiguous and undesired +groupings, which is considered inferior. -- cgit v1.2.3