diff options
author | Sven Gothel <[email protected]> | 2013-10-15 15:36:03 +0200 |
---|---|---|
committer | Sven Gothel <[email protected]> | 2013-10-15 15:36:03 +0200 |
commit | bc72e232a4b74c2be8c91c540a7b6153bfefb8c0 (patch) | |
tree | a96ef243eb96fad1ca9d304eae6b3479c8d1facd /doc | |
parent | 5ac6d508c7208ac4fe5d057a9ea1bdcba5f7b998 (diff) |
Bug 861 - NEWT: Unify MouseEvent Processing incl. gesture processing
We processed MouseEvents within NEWT as follows:
sendMouseEvent/enqueueMouseEvent -> doMouseEvent,
- called by native code to be delivered via consumeMouseEvent (now or later)
- events are validated (move/drag, boundaries)
- missing events are synthesized (click, enter, ..)
as well as in several factories, i.e.:
- AWTNewtEventFactory (1:1)
- AndroidNewtEventFactory
- synthesized events .. (click, ..)
- android typed gesture detection (drag -> 1 finger scroll..)
The latter enqueues events do Window/Display directly to be consumed by WindowImpl.
Then users may have their own gesture detection etc.
+++
This change unifies mouse/pointer event processing within NEWT within consumeEvent(..)
which represents a common entry point.
Gesture processing is now realized w/ a public API
- GestureHandler
- GestureHandler.GestureListener
- GestureHandler.GesureEvent
which supplies:
- default impl. of optional gesture handlers (scroll, .. - default: enabled)
- public API to add/remove gesture-handler and -listener
+++
This allows our impl. to scale better in support of
more multiple pointer devices (-> Win7/Win8, X11, ..).
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions