With this, the value passed to suggestedWords is never null.

Bug: 8636060
Change-Id: I433dd7e7290125e217e05cc20bee7a4b58fe083f

The goal is to remove the function completely.

Bug: 8636060
Change-Id: I50b8f0368c8f6506209398ff931881e2235c3d2d

This should be what was intended.

Bug: 8636060
Change-Id: I20a1cc4f0b1fb9444fb6f9a20ef727e3d1a3a880

When the app goes to the trouble of supplying completions,
but supplies null, then we should show punctuations if
settings allow.

Bug: 8636060
Change-Id: I33c32566039c80df61fcca3fab346fd336d96a12

Bug: 8636060
Change-Id: I5cac787953a3c71b6402520c2f5c70619d4a40a8

The coming string of changes is very complicated, so
I'm going to do things really slowly.

Bug: 8636060
Change-Id: Id8a07a154ac514e9b3307ead22d47c3ae6fa732b

Change-Id: I6e16b4e05010a08f4d1da34145f819c32b3bc79e

It seems the comments were right all along. This seems to really
be useless.

Bug: 8636060
Change-Id: Ie030e9cb73007334380d023abeaa4ce52a863a34

Bug: 8636060
Change-Id: I5092942ab4fd6aaf37023083040cadbc18583fd1

Bug: 8636060
Change-Id: I931c553f68a1f15d22711a661dbffd4e5d421979

Bug: 8636060
Change-Id: I7290250637e37bf6964bab71d2141e19f20a5459

Bug: 8636060
Change-Id: I4ce5c9b62181ce8593a453ce222ae7d1fdc08f07

Bug: 8636060
Change-Id: I2a5da27e73cf378e55bd80ab2054c1ba8b13f6ec

This reverts commit e7ee4fa8.

Change-Id: I56fab60ac859289d3ed51f691cd7e2a15da01856

Bug: 8636060
Change-Id: I3c5213cc57b5b5febd25f14d40c197d2da43dfb8

In some ways, the delete key on the Emoji palette was
inconsistent with that in other keyboard layouts.
- It deletes a character in down events, not up events.
- A user cannot cancel the event by moving the finger away from
  the key.

This patch fixes these inconsistencies by revisin
EmojiPalettesView.DeleteKeyOnTouchListener. Notable changes are:
- An explicit state machine is introduced because there are
  different event sequences to be considered.
- Background thread is replaced with CountDownTimer so tha
  key-repeat events can be naturally generated in the UI thread.
- MotionEvent.ACTION_MOVE is now handled to cancel the
  subsequent delete key events when the finger is moved away
  from the key area.

Bug: 12464067
Change-Id: Ibc360a1394afef368a8d9af7b4c0e99e8ce1d83c

Change-Id: I4ba261752750f5087cba810045669512b430b5e0

some cleanups as well

Change-Id: I92252eb7b13cb70283a79f50429ed77405ea9575

Bug: 12602903

Change-Id: I1ea4e558b6d2fde425ce28226647ad60095e3488

Removed an unused method too.

Change-Id: Id364009fd4e94ec65862fc3651a181e862909a42

This is a followup to IL69.

Change-Id: Iba154517aa7f75b9f16aa1b808c0da8d84be837f

Change-Id: Ib5a8be5d9ac508d57648e4e8811805eea4355fc3
Auto-generated-cl: translation import

Change-Id: I6c8aa53b9be4c3aa5822a820cc8cfdc3cf31c390
Auto-generated-cl: translation import

Change-Id: I382abd3104d535a1e868935d8cfb4e34ad8ebaed

This constant is better located in SuggestedWords.
Or it could be in Constants, that would be fine too.

Bug: 8636060
Change-Id: I3e721bb1e2559f028dce8929eceadfe0478c5924

Followup to IL66

Change-Id: I067e72c36f483cc3e3b24736c01843531298b507

Please hold my gun while I have this nice cup of tea.
Yes !!

Bug: 8636060
Change-Id: I33c8ffe51bb2106b17f7941235ad1e427e3a81f7

Bug: 8636060
Change-Id: Iec56bce362ebfc52fedab02b127978abb4f3c7f9

Bug: 8636060
Change-Id: I624a45500603dfad355ee3b8b794b2d895219c0b

Bug: 8636060
Change-Id: I242b7c264abf380bcd6b6b3c848238921f988e54

This is necessary for tests

Bug: 8636060
Change-Id: I50ea401a22e4df72333eda61ca39aa180966ee4b

Bug: 8636060
Change-Id: Ib13a54854e30afb79217a0a1f2aeca50a95ba155

Bug: 8636060
Change-Id: I3b144993e2bcd552f9b292b8f057c9db4216125c

This works because getKey{X,Y} is a no-op on
Constants.NOT_A_COORDINATE.

Bug: 8636060
Change-Id: I2f7dd96b6011f094110f7978f8ff24ef2a6e2585

Bug: 8636060
Change-Id: Ic051e5d5514d270101b0571a2d30e2caa8f85bc1

This also fixes the coordinates passed to logOnDelete and
log onSeparator.

Bug: 8636060
Change-Id: I4703d61ad7de76b501adca18df3a69e06450c9a1

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

Change-Id: I4103541d99fe59bfcf12379a1298a0a690497846

The newline string resource "\n" doesn't work off-device simulation.

Bug: 12623502
Change-Id: I3ad63d8afe50be174493d43f00f7191062c87cb7

Change-Id: I78d488ad84a11af809ee1f8d3d2fa01a89fbfa28