| 4c971c001f401d7742db326c8e5654693eb3687e |
|
21-Oct-2015 |
Michael Wright <michaelwr@google.com> |
Limit the number of keys read by KeyCharacterMaps.
Apps can send us a KCM containing a ridiculous key count, which will
cause us to crash when an allocation fails. Limit the key count so this
doesn't happen.
Bug: 24876135
Change-Id: I2bb4a5acabfc9184a867a406eef756c28c28f0ad
/frameworks/native/include/input/KeyCharacterMap.h
|
| 3b9211608669eb5aafba65d35b4cfbec89755499 |
|
08-Oct-2015 |
Dmitry Torokhov <dtor@google.com> |
resolved conflicts for b9163905 to mnc-dr-dev-plus-aosp
Change-Id: I83afd79491533b1c7ae2aed50a927db175ba555f
|
| 115f93eeebf7f33b56ed090de70d6e8c733e5d88 |
|
18-Sep-2015 |
Dmitry Torokhov <dtor@google.com> |
Allow defining replacement key events in keymap
Currently keyboard maps allow to assign character sequences to key
events and allow specifying a so-called "fallback" key events that are
re-injected into input stream if target application indicates that it
was not able to handle the original key event. Unfortunately there is no
way to perform substitution before handing the event to applicationis.
This change adds a new keymap keyword "replace" that allows users query
"replacement" actions for key (if any), with the intent that such
replacement happens early in the event handling process.
Bug: 24504154
Change-Id: I3e6a2476c856524171df00ad22ff56f2018c1278
/frameworks/native/include/input/KeyCharacterMap.h
|
| 6071da7ef84c60645572654504813d492b8b21d5 |
|
13-Aug-2015 |
Elliott Hughes <enh@google.com> |
Lose HAVE_ANDROID_OS from frameworks/native.
Change-Id: I8e6af2a46a9d875192fc7957ada9b5f66d84bad6
/frameworks/native/include/input/KeyCharacterMap.h
|
| 5912f95d26f77d2b6df13e1f2672e48e3f9b871c |
|
02-Jul-2013 |
Jeff Brown <jeffbrown@google.com> |
Move input library code from frameworks/base.
Change-Id: I4983db61b53e28479fc90d9211fafff68f7f49a6
/frameworks/native/include/input/KeyCharacterMap.h
|