It's useless to setAutoCorrection(getTypedWord()). Every time the
contents of the word composer are altered, the auto-correction is
reset, and at use time if it's null then the typed word is used
anyway.

Change-Id: I0870657a1ab3f456f376995b27e70703f7a5d23a

Change-Id: I33f4042265c0dcc2530cee43c610f73ec99c6792

Essentially this does activate auto-correction with a hardware
keyboard, although a lot of things are still left to implement.
No proximity is used yet which means only missing and excessive
letters are considered. Dead keys are not handled. No combiner
is supported. No suggestions are displayed. Resuming suggestions
does not work correctly with a hardware key (because the view
holds a temporary hardware event 'onKeyPreIme' and the event
from the IME won't be handled until this is handled which won't
happen until after the IME said that it did handle the event).

Bug: 5037589
Change-Id: Idcb5c7b26d56717ed772d53c062362807f11cdae

Bug: 5037589
Change-Id: I829f70a258de58ef8d2b836a9b435198a226e37f

Change-Id: Ib0de800599ae7f12c86270a627616d5b52366414

In this test, it's impossible that start < 0 so the test is useless.
I'm not sure what the cursor test was for, but it's very old code, and
it seems the assumption was either misled or doesn't hold any more:
testing for the absolute cursor position against the length of the
word against the cursor makes no sense.

The net result of this was that when the cursor index got large
enough, resuming suggestion would not work any more.

Bug: 7586467
Change-Id: I3462082374fe9579bec7698f4d424de6ff5f2ded

Bug: 7675452
Change-Id: I2121f56964b6d25e8d40f5b8ec67eeae527b2117

Change-Id: I41e0a95437aa9b8ec9a8eefb3bc5eb0452284b60

Bug: 5037589
Change-Id: I0a4926f94ef8d1caa17669801608608648b697b9

Leftover from changing variables from CharSequence to String

Change-Id: I4db43fcb075aa37bf9c5b2a23bad0e4c2d718379

multi project commit with I5847d4aba97a7224ae170a7153811c5a11816449

Change-Id: Ie6fbf6f19f0193451fe6f3ddf9d4ef1637a35db1

Change-Id: I73a6009294a4f559a93b6ea9ceb4ea2683d97486

Change-Id: Ic46c91374ae0177cafad4579d28d6980af0d8d3a

Change-Id: I73b7765c764e5f1035f1c37df45345f26aa5acb1

Change-Id: I2c59983236c936b8698004db8213b68c2f964cd5

Upcoming changes require LatinIME class, not just InputMethodService

Change-Id: Ia5b3a716ac02a99749fb2ba0164ba46c8a0c559a

Previously, LOG_EVERYTHING logged both all bigrams and also the entire TextView at the end of a
session.  Now, use a separate flag, LOG_FULL_TEXTVIEW_CONTENTS to determine whether the TextView
contents are recorded.

Change-Id: I0c7a90a8ff88aa65d057f3b2d3dd5adc3893504a

Change-Id: I31c5520598269a83ab218e3a024bff0a625c2770

Change-Id: I70d5bd0cb12be7a5cc216799f92622912646466f

Change-Id: Idd786e2804dc82c1fa27ecf0fc0537491438d017

- count how many times a gesture is deleted
- count num chars entered by gesture
- change name of fns to reflect capturing gesture information when setting composing text

Change-Id: I1b8ebf9cfcf304e0efd827c8b8e28a4010199728

Move specifics of Log output format from ResearchLog to LogUnit

Change-Id: I9d0253c50bb8175ab141bd87dd9a09f39f316b10

This NPE issue (Bug: 7903331) has been introduced by Ie68c7698.

Bug: 7903331
Change-Id: I44884f5608fe47d9db7a2c93a752d17b9ae39a22