2b38b5e8e6
This is fine because getKey{X,Y} is idempotent for any
non-keyboard coordinate value.
However this makes a net change : the x,y values passed to
LatinImeLoggerUtils.onNonSeparator are now different.
The point is however that they used to be wrong. The logged
values used not to account for the keyboard padding that
is present on tablets, and in the simulating tools we don't
know about that padding so we couldn't use the coordinates.
The catch here is that other calls like LoggerUtils.onSeparator
should follow suit, but this is too big a change to do it at once.
Follow-up changes will fix them too.
Bug: 8636060
Change-Id: If4b3d3cb1ed4b44c35f23e66aba3b5797236bba7
|
||
|---|---|---|
| .. | ||
| res | ||
| src/com/android/inputmethod | ||
| Android.mk | ||
| AndroidManifest.xml | ||
| MODULE_LICENSE_APACHE2 | ||
| NOTICE | ||
| proguard.flags | ||