| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \
| |/
|/| |
|
| |
| |
| |
| | |
Change-Id: If2f7bd1346cc5085bf57645830f0faac44d017e4
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| | |
Bug: 6669677
Change-Id: I447668932de118b158fa029ddc977b3f3cc06cb8
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The documentation for setComposingRegion states explicitly
that it does not move the cursor. This is just a bug.
This does not have any ill effects right now, but it will have
in later changes if not fixed.
As for the selection handling, the specific test that this code
removes used to serve a purpose, but it does not any more because
the code using the value has been much sanitized. Now the variable
can just take the obvious value, and become so self-explanatory
that the comments are unnecessary.
Change-Id: I548d899b38776bd3ab5f5361aab0d89d98f12e73
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I5cad5d5814303d7ca4abadd3fca1c37bd1bc357e
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
SpannableStrings are not the only type of Spanned, they are
only the mutable kind. SpannedString is the immutable one.
Spanned is the correct class to use there.
Bug: 8839763
Bug: 8862327
Change-Id: Ic5e6199a51f22368914f2748ac2d0d1ca6a33f78
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
in the hope of avoiding UnsatisfiedLinkError. This is definitely not a
confident fix as we still don't know the root cause of the issue.
bug: 9325110
Change-Id: I1abf8031b98509f63fce6a2d069d497895ea712c
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I1c5b27c8edf231680edb8d96f63b9d04cfc6a6fa
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
|
| |/ / /
| | | |
| | | |
| | | |
| | | | |
Bug: 9534022
Change-Id: I5ab575c724fd7a9e80c76a93d83949e81b2970bb
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This changes how the Range class stores its data, but not its
functionality. It also improves encapsulation a bit.
Bug: 8839763
Bug: 8862327
Change-Id: I5bd583b3fc96a99b93a2632882d8fd587c03ab76
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | | |
Bug: 8689779
Change-Id: Ia78d3540f44ec0028c3246a8e0163e9ecf061ecf
|
|/ /
| |
| |
| |
| | |
Bug: 9508186
Change-Id: I8f0fbf4e0578cf9116d4c57e7e5747d38c89387e
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| | |
Bug: 8526576
Change-Id: Idd6f9cd076d5915361c68f5c29afbba67dd54eba
|
| |
| |
| |
| |
| | |
Bug: 9475973
Change-Id: I6ae825b161dde69e19b52d73fb9aa782e2aa7423
|
| |
| |
| |
| |
| | |
Bug: 9468462
Change-Id: Ifa46a56873c10888da8eaa2782fe07ef138a141b
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This cuts the time spent in computeNearestNeigbors by
a factor of 6 to 20, with an average at about 8.
This method representing about 25% of the total time
spent when switching keyboards, this change is a
20% improvement in layout switching time.
Bug: 8689779
Change-Id: Icb465f6010b317c7156057891c3341e51a198688
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
As a preparation to show "system default" in the settings. LatinIME
can't know the actual system default value.
Bug: 9468462
Change-Id: I0b7898d1ca29ded7a619dd636d2ad16eb0db292e
|
| |
| |
| |
| |
| |
| |
| | |
This is a shameful bug :/
Bug: 9410367
Change-Id: I54ddbcd0323fa2c11fbd2aa8a1b3d2e07f6e83c8
|
|\ \ |
|
| |/
| |
| |
| |
| |
| | |
b/9422713
Change-Id: I4880fad6a5b10d09ca11b63311f14862bee724e5
|
|\ \ |
|
| |/
| |
| |
| |
| | |
Bug: 9410958
Change-Id: I966e452c6dbdcb444abbb6ffb316849a7c85a73b
|
|/
|
|
| |
Change-Id: I202a25da4e1a722aa35c57665d73bc5990404c4e
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This will spare a lot of IPC for Latin IME at the cost of very little
retained memory.
This improves the loading by potentially a lot - between 15 and 30%
when the layout is cached (which should now be the case almost every
time), and half that if it's not. More importantly, it makes the
load time less sensitive to high device load, which is one of the
sore points.
Bug: 8689779
Change-Id: I2e07736f1a92c38eed0e203bc690761a181da8b9
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: 9305379
Change-Id: Iab32753070a056d3861a45aa898911b7ab67dfb6
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
This is to avoid confusion if multiple IMEs are installed with
dictionary pack components
Change-Id: Ibc91951e4fdd5db13f681e4cb06197da98527bbc
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | | |
Change-Id: I4f08632d97f182d312edc82bda3c3897a71099ad
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the logger feedback screen is up and the user hits the home button or the
keyboard otherwise closes, the system won't let the user enter feedback again,
because it is waiting for the user to finish the first one.
With this change, the state associated with the feedback screen is
cleared when the user closes the keyboard.
b/9398772
Change-Id: I832a82793ad42e31b6b3fdb04fabcea75facde7d
|
|/ /
| |
| |
| |
| | |
Bug: 9374496
Change-Id: If74306104e9d25288e1b216a328304da376c1bdb
|
| |
| |
| |
| |
| |
| |
| |
| | |
This typically improves the average loading time by about
35%, after the first time.
Bug: 8689779
Change-Id: I7b0ab6b942af1d3250b9dcbf875f27f9f64692f3
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 9314901
Change-Id: Id80f59df38ae72766b097fd1c23326fedd302439
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In setup wizard, InputMethodManager may not be able to be aware that
this IME is installed, especially just after the IME is installed via
GooglePlay app and hit the open button on the app to launch the setup
wizard.
Bug: 9299618
Change-Id: I00c8544178b41074253d49ae9481996ec56593d2
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 9318351
Change-Id: I55338c001070655a3f90df3dbe1351bd4180d520
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a bit of a shot in the dark, as I really don't see how this
can happen, but this should fix it in the correct way no matter
how it's actually happening.
Bug: 9301836
Change-Id: I472865b7a78883942c9fd46773238c23788674f8
|