History log of /frameworks/native/libs/input/Keyboard.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
61da25aa581d2d7994b9d727b5e6f9419df68c8a 16-Feb-2018 Siarhei Vishniakou <svv@google.com> Move SPECIAL_FUNCTION from .kcm to .idc files

Currently, the only use of device-specific .kcm files is to specify
SPECIAL_FUNCTION flag (meaning that this keyboard is only used to
perform system control functions and not for typing).

Instead of adding a special .kcm file, use .idc files with se
keyboard.specialFunction = 1 to achieve the same functionality. This
allows the removal of all device-specific .kcm files.

The .kcm functionality will remain in P (with a warning). The
functionality will be removed in Q.

Bug: 67718661
Test: tested the codepath on Android wear device via logging
Change-Id: I1b4572456fa42caae1282dd8d3557820671b3610
/frameworks/native/libs/input/Keyboard.cpp
9e94788e8a8388eeb1113dc42c932ed42008de5d 06-Mar-2017 Frank Barchard <fbarchard@google.com> InputDevice warning fixes and make warnigs into Error

use const char * for string literals in InputDevice
Remove unused variable in Keyboard

Bug: 35993509
Test: mm in frameworks/native/libs/input builds without the warning
Change-Id: I11242835eae855386c47e56d6c36e5a2f912a28f
/frameworks/native/libs/input/Keyboard.cpp
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/libs/input/Keyboard.cpp
872db4f11e407accccba9d37c335ef7e3597eba4 23-Apr-2014 Michael Wright <michaelwr@google.com> Move key attribute information out of native.

Native doesn't ever actually care about the attributes of keys, so
move all of it up into the managed layer and move all of the key
names down so they're defined once.

Change-Id: Ic8ded13ce050b2b98744735ff50d11e8d882d7d5
/frameworks/native/libs/input/Keyboard.cpp
74bdd2e7ceabd3c9e74ccf7c2e6bd3dae27ca497 18-Oct-2013 Michael Wright <michaelwr@google.com> Parse LED mappings in keylayout files

Change-Id: I6bc3760341868015f054d9866e2616a312da94e0
/frameworks/native/libs/input/Keyboard.cpp
5912f95d26f77d2b6df13e1f2672e48e3f9b871c 02-Jul-2013 Jeff Brown <jeffbrown@google.com> Move input library code from frameworks/base.

Change-Id: I4983db61b53e28479fc90d9211fafff68f7f49a6
/frameworks/native/libs/input/Keyboard.cpp