Bug: 13406701
Change-Id: Id9a2e4144b1908ad27d78228ee19e6fc4d4d669f

Bug: 13778001
Change-Id: I3ebd57950cdfacbbcdc64ed214c0590519a0665c

Bug: 8636060
Change-Id: I696514934586ee71e734fd974026af8b2c866127

Bug: 8636060
Change-Id: I169618b50532df68e973e14b3f114c6c19714c84

Bug: 8636060
Change-Id: I36ba3e00630bef644fc4671d0714490b5982f6a1

Bug: 8636060
Change-Id: I2f55fc23d7e05b63582a3f0660b58635eae5ec59

Bug: 13710224
Bug: 12821388
Bug: 12667742
Change-Id: I6188e0240193d2bca789110e7660a0f31bbafc62

Bug: 12667742
Bug: 12821388
Change-Id: Ic0bad56fb96e54ac032759adffc8ea320c06dff2

Change-Id: Ia11d656a70623168b091763ac6524750f9cca8d8

Bug: 8636060
Change-Id: I088be9a7555265ca097667523defd73be4cbe37f

Bug: 13622107
Bug: 13406701
Change-Id: I0023b398c4451253f9f717e2bd990b8a054004bc

Make mSuggest final and give DictionaryFacilitator the
responsibility to manage dictionary loading state.
This can simplify the logic to decide how to deal with
additional dictionaries when loading settings or language
switching.

Bug: 13273534
Change-Id: I9f3d328272f25addfa186fbeedaaf8417455ba99

Change-Id: Ie5da6c73d4df4553067c58cd0dce9abb34534250

Bug: 13406701
Change-Id: I3b9f75de9283f76366d1bef7e14a8f22f2186669

Bug: 8636060
Change-Id: Ie193b747bd9d0b5ba6a986b9a3c746c2182742ed

Bug: 8636060

Change-Id: I55332c22897e97148621cbd367acf5175b5b3d04

Bug: 8689779
Change-Id: I2cf10c690c7e4a9c6bf27211d1fccc1f9d4a9249

The event interpreter should intervene later, after decoding.
Decoding should happen first, and then the Event should
be passed to the InputLogic.

For the time being, we will leave the (unused) EventInterpreter
class and its friends, because we'll use them again later.

Bug: 13406701
Change-Id: I7582d486724311e39e6692e606cca50c78800643

Bug: 13406701
Change-Id: I9ecd2709c8f1c678a85b0cfaf7c5ed4f78459821

Bug: 13406701
Change-Id: I0a0e4e0b3357f116e1b915c548dee4575e300c92

Bug: 13406701
Change-Id: Id82e9aab6544ca308e6ac6dee2cfa018b9ce2d8f

Bug: 8636060
Change-Id: I29ce4c82ea880a937b1c9e5daf494fcdbbdd1336

A transaction should always operate with a consistent set
of settings. It's better to have it reference them than to
always pass them along.

Bug: 8636060
Change-Id: I3c642dfea6be30712fc6cbb279c64f3185895791

Bug: 8636060
Change-Id: Icdf87995dedec410b54c306e8d312ba7ec25cea6

Bug: 13303965
Change-Id: Iedc5d38f70af76fbebb99e59a0d17c1e226c810d

We probably can't put this off any longer

Bug: 8636060
Change-Id: I1e5d3cf62d719f4d064ced3282bebf2e822f6baa

Remove useless arguments, local vars, make stuff private

Change-Id: I7cc6c19e9c1703304d593e02be31eb9569cc7b4e

Change-Id: Ia84d3e5a102e1056e3d7467be07df89390f17617

Bug: 8636060
Change-Id: I944b10ec9798eec57d986e1075ba348aa0892cae

Bug: 8636060
Change-Id: I0d8f93985ddc6e93ce9af0d92a8056620351a498

...and improve encapsulation and readability.

Bug: 8636060
Change-Id: I36407630b307df0721ea7fdb7e7a22cdf2b018b3

Bug: 10385162
Change-Id: Icf9471d474a3a8ed8f38c46c7948c66f9131691e

We already have a mechanism to avoid this crash, but it wasn't
used every time it needed to. It's possible that ending a batch
input and starting a batch input happen while suggestions
are being pulled out, which would result in pointers that have
been reset being passed for trimming.
Just increasing the sequence number should get rid of the
problem.

Bug: 12178124
Change-Id: I36ef3bc8a78679bc09daa39e665f5ce1bab50c2a

Also fix a small cosmetic bug where the suggestion strip
would flash.

Bug: 12951777
Change-Id: I68b7bb9175571de9c718f737eebd9f67ea04a931

Bug: 13107471
Change-Id: I47df79bc6f015c212d1b6d2f63b2efc5da24294e

Less code, less chance of stuff escaping, and a bit of a clarification.
Yay.

Change-Id: I3193fd8ad7ac28195260cbc231c4e498a63a460c

Bug: 11447084
Change-Id: I5bd558b9dd85d1505aa918f44e8ac3e52ec42d97

This change must be checked in together with I366c477516.

Bug: 12640318
Change-Id: I8d3864b9d9649c9e3306e82b01a6327b11281b1f

Some apps depend on the keyboard sending something to them
when the text is empty. This is BROKEN. Your app must not lie
to the keyboard about what is before the cursor. If there is something
to delete, you must not pretend there is not and try to catch some
delete event. This will result in a bad user experience. This will not
work with all IMEs. If your app needs this broken behavior, you're
doing it wrong. Seriously guys, we're not in the era of typewriters
any more, there are touch screens, there are gestures, there is
accessibility, there are many innovative IMEs that don't have
keys. Do *NOT* rely on key events.

This change implements an ugly hack so that these broken apps
may continue half-working with LatinIME. We are very unhappy
about this.

Bug: 12998568
Change-Id: Ia62ae2fbee4fee65b463acf3a79aafcfd0defa1d

This fixes two separate problems:
- The word finds itself with two separate suggestion spans.
This is fine for LatinIME, but it's hard to predict whether it's
fine for other interested parties (other keyboards).
- The test for the blue underline was incorrect.

Change-Id: I3ecc849676851bf25a25238d694adaa956521a26