The gesture recognisers are arranged in a list so that the correct gesture recogniser gets the opportunity to detect the gesture in time. An axample of a set of gesture recognisers could be e.g.

|---------------------------------------------| | scrolling stop by tap -gesture recogniser | A is enabled only when needed, when enabled must precede all others | | (note that locking partly can be used to achieve the same) |---------------------------------------------| | location specific: zoom + button tap gesture| B these must detect the location first |---------------------------------------------| | location specific: zoom - button tap gesture| B these must detect the location first |---------------------------------------------| | location specific: edge scroll gesture | B these must detect the location first |---------------------------------------------| | pinch zoom gesture | standard gesture, but application wide (spans windows) | | C another requirement: disable all but me/restore state | | so that other gestures will not meddle in while pinching |---------------------------------------------| | hover gesture | C standard gesture, needs to detect the EMove speed |---------------------------------------------| | pan gesture | C standard gesture, but must be after hover |---------------------------------------------| | tap/doubletap gesture | C standard gesture, order not that important, since | | needs just to see certain events in history: touch/release |---------------------------------------------|

The order of gesture recognisers determine how the system behaves, so there must be an easy way to define the order. The order could be defined either by specifying the IDs or just their types, if then the order is not that important. TODO to study whether it would be a good idea to implement this so that there are separate lists for the three different classes of gesture recognisers A, B and C; this might make the implementation simpler.