Bug: 6465474
Change-Id: Ifbfe0ddc2ce5fab070939ede3db7bf03a8535a45

Bug: 6105732
Change-Id: I92e7a9c6d6eb648f747c3b396d7993479fd8478a

Change-Id: I10a634f7492b45d5a72345f14d36cf341946387d

Bug: 4343280
Change-Id: I82f7d08703647a3492ce6e2d3b741146df58927e

Bug: 4343280
Test: Ib43c0f1d1a19d067ea0

Change-Id: I3393a6099cb7fb824994f4656ccfef884f9c6bc4

Bug: 6236912
Change-Id: Ie09e5ef1c23eb48621ac3f2f2dc28dc2e46ca288

Change-Id: I66b61cbe491cf8375144e834390beae3209a777d

Change-Id: Ieb6af8385356e259720b50f1fe46a694a098b30f

Man that was bad, it's heavy, it's called quite often, and it's
totally useless

Change-Id: Ia7e23e0e60ff4a929b226f3f4ccabedbc3ea2c06

This results in the computation being done in native code
and the correct proximity being used.
Bug: 6181080

Change-Id: I08fa05c781d607e4feca2caeda353ec19c133a3d

Bug: 4343280
Change-Id: I57c0f9e20d9d8911009ea97057251a7f7a81512f

Bug: 4343280

Change-Id: I6adaf560f7a4f1f96dcb6ec2f61f20ee3001167e

Bug: 4343280
Change-Id: I4e2dfb00d9c843a8a285d409ac5ab8fca5fb1694

KeyDetector should use the distance from the hit box to detect the
key.

Bug: 6174250
Change-Id: Id1745d90222d1d1a10467f194b45307c12449944

Bug: 4343280

Test:  I11f8518d9ee

Change-Id: I4b90bdffffed9736af223ac83c1a54019add70bb

Change-Id: I2c8b093b59ad36ffe860c3c4d360d87251d101c4

Bug: 4343280

Change-Id: I0f6a7e6912ed4abea07c10d266da4c7ccb0dae76

This finally makes active the behavior described in
Bug: 5968922

Change-Id: I363ed23270c3dea75411ea806011225097b5d07c

This stores the separator that was used to commit the word in
the LastComposedWord. It may be NOT_A_SEPARATOR if there was
no separator (for example, the cursor moved causing a commit,
or there was a manual pick). This is necessary to implement
feature request #5968922.

Change-Id: I5fcf19a78ec66d68d4df89418eaef13952588207

There is no point storing the prospective autocorrect - we are
recomputing it anyway. The committed word however will be necessary
to implement feature request #5968922.

Change-Id: I588c18e1a5a1050a791d601de465f421ccbe36cd

Change-Id: I61ff218ae2ca4eb443a370e581b677755258670a

Bug: 5961179
Change-Id: I452efc552c6ab390931f25557d7aee5a64bf054e

And unit test

Change-Id: Ic4fc3626f8b86e10156d770d41cd6deab5d31f39

Seems I didn't get how to iterate on a String correctly >.>
Talk about a big bug. Anyway, I think it's working now.

Bug: 5955228
Change-Id: I988c900cf2a16c44b9505cfd4f77c7cda7e592f0

Change-Id: Ifbe0d7e4eafea1926bbce968eae4724dd5769689

It turns out this can be removed entirely.

Change-Id: I6f23703cef1666311989a825285317eef696487f

Deactivate the LastComposedWord when the commit was not the right
type, instead of fooling it by passing it a null auto-correction.

Change-Id: I032b477dc691bd151a644ca4b0c9f0a9b5512e45

Remove the now useless WordComposer.CharacterStore class
and merge back its members inside WordComposer. This should
simplify the word composer a bit.

Change-Id: I5fe32418c62a583cd558dce98758a4701559bdf5

This is cleanup.
This also introduces a "deactivated" state to the last committed
word, that can be used for
Bug: 5875776

Change-Id: I1855adb8ac8123f6d2c5365b0ae899145e5c3ba1

Change-Id: Ia62ef33b5c777a258b02280bda1b8368780a7eef

Change-Id: Ie0ea02a061dd0cb84db5f33113ff433584636bc7

Change-Id: Idf47f2e2bdd1d6394fc4b1ab7df28d64a808da1e

Change-Id: I87498799e6a48b8fa65924a098bb0ceb7626dce1

Change-Id: I16fa4099c75faac35344b0e4d3c2b866ddac896a

Auto-correct cancellation would sometimes kick in at
wrong times, causing crashes.

Bug: 5784542
Change-Id: I68dd6b8d9237ce9b66af2dc63e77ba6dd5fd69dd

Change-Id: I31cce9db471dcd4a7b3477bcb037a8ff482b7696

Change-Id: I68c667b00dadf2ed9f1c62fb7da37d2cf499cd81

...instead of the hard-to-understand mHasUncommittedTypedChars.
This is possible because now the word composer is actually aware
of commits.

Change-Id: I36b664ce8402a280f801e87b9ebe161f416b0853

Change-Id: I04e691fbc9227d4df195429bca89edea93575347

Currently, these variables hold the info about the composing
word, or maybe some outdated info, and it's not very clear
which it is. LatinIME is maintaining the freshness info in
a separate boolean, and uses it throughout the code for many,
many things, leading to much confusion.
The idea in grouping this info is, it can be saved in another
instance and restored later. It can be tested against to know
whether there is actually outdated but kept info or not, and
it should allow to straighten out what is actually currently
being typed. Ultimately, it will eliminate the need for
LatinIME to keep track of the status of the info in the
word composer.

Change-Id: I00e2c690f303f8320c9be35590a6df4583e9e456