| fc2ebc473bbca6f9e6e30ea5de979c4852f35319 |
|
06-Aug-2009 |
Iliyan Malchev <malchev@google.com> |
EventHub: pass the name of each input device up to Java
Signed-off-by: Iliyan Malchev <malchev@google.com>
/frameworks/base/include/ui/EventHub.h
|
| 0dd7cb4b4ef86eb7d4e837b1948501da66adeebe |
|
04-Aug-2009 |
Dianne Hackborn <hackbod@google.com> |
Finish implementation of multiple pointer support for MotionEvent.
The major things going on here:
- The MotionEvent API is now extended to included "pointer ID" information, for
applications to keep track of individual fingers as they move up and down.
PointerLocation has been updated to take advantage of this.
- The input system now has logic to generate MotionEvents with the new ID
information, synthesizing an identifier as new points are down and trying to
keep pointer ids consistent across events by looking at the distance between
the last and next set of pointers.
- We now support the new multitouch driver protocol, and will use that instead
of the old one if it is available. We do NOT use any finger id information
coming from the driver, but always synthesize pointer ids in user space.
(This is simply because we don't yet have a driver reporting this information
from which to base an implementation on.)
- Increase maximum number of fingers to 10. This code has only been used
with a driver that reports up to 2, so no idea how more will actually work.
- Oh and the input system can now detect and report physical DPAD devices.
/frameworks/base/include/ui/EventHub.h
|
| 1d9dfc5dcf459e85cffcb762ffdb9b9a4abbfd67 |
|
16-Jul-2009 |
Mike Lockwood <lockwood@android.com> |
EventHub: Add support for excluding devices from being opened by as a keyboard.
This will be used to avoid unnecessarily listening to data from sensors
that function as event devices.
Signed-off-by: Mike Lockwood <lockwood@android.com>
/frameworks/base/include/ui/EventHub.h
|
| e3dd884815b2aaeec4241859722ab603e0b1466b |
|
14-Jul-2009 |
Dianne Hackborn <hackbod@google.com> |
Implement virtual button support.
The kernel can now publish a property describing the layout of virtual
hardware buttons on the touchscreen. These outside of the display
area (outside of the absolute x and y controller range the driver
reports), and when the user presses on them a key event will be
generated rather than a touch event.
This also includes a number of tweaks to the absolute controller
processing to make things work better on the new screens. For
example, we now reject down events outside of the display area.
Still left to be done is the ability to cancel a key down event,
so the user can slide up from the virtual keys to the touch screen
without causing a virtual key to execute.
/frameworks/base/include/ui/EventHub.h
|
| 3b4062eeb01be33951ba214e027da523cf09f8b1 |
|
01-Jun-2009 |
Mathias Agopian <mathias@google.com> |
get rid of utils.h
/frameworks/base/include/ui/EventHub.h
|
| 9066cfe9886ac131c34d59ed0e2d287b0e3c0087 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/include/ui/EventHub.h
|
| d83a98f4ce9cfa908f5c54bbd70f03eec07e7553 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/include/ui/EventHub.h
|
| d24b8183b93e781080b2c16c487e60d51c12da31 |
|
11-Feb-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake/...@130745
/frameworks/base/include/ui/EventHub.h
|
| 9266c558bf1d21ff647525ff99f7dadbca417309 |
|
16-Jan-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake/...@126645
/frameworks/base/include/ui/EventHub.h
|
| 54b6cfa9a9e5b861a9930af873580d6dc20f773c |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/frameworks/base/include/ui/EventHub.h
|