| Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Ifd0d5b6978f76b841574a6e10157c32d0cd656b6
|
|
Stop storing an int in each of the different class types, and
just store a string in the top class.
Change-Id: I2af1832743e6fe78e5c1364f6d9cc21252bf5831
|
|
Change-Id: Ic1a198ab1b4f0323fde9e4245729fd0e6011b914
|
|
Change-Id: I106a858f0be7452dd89f425805a6f72aa88c3f65
|
|
We want to get rid of all those IDs in Latin IME.
Change-Id: Ibe08100a5e2976c80abb049889233b4047a686f3
|
|
Yay.
Change-Id: Icf686eb2d675da959f19edc856b521e6288dcea3
|
|
Change-Id: Ic4b0ae05cd98a1aec5806c5e4b744158e73aea7a
|
|
multi-project CL with Ib5b544b9b2d8b0e4419238976b2e274e5ac564f8
Bug: 6188932
Change-Id: Iea68cf36924d6fda126130a98431a6ce02ba251e
|
|
This special casing is useless. If the word is the same as what
user typed, the scoring algorithm already ensures that it comes
out at the top. Actually, as is written in a comment here, code
executed later is actively relying on this suggestion having
the top score ! There is no need to test it for equalness and
inserting it at the top then.
Change-Id: I263a6de59b77ec72a2dcbb933361b8e16fca0681
|
|
Change-Id: I5ca77ed65e95a6d357215c0e730238fb463986bb
|
|
We already had that computed
Change-Id: I2a9742eaee2e9db1f73aeddda7bae7e237b4d15c
|
|
Change-Id: I1dc668698a5cd840297e713a26a525f5e32d35d6
|
|
Change-Id: Ibf5f3e40da55998364d0d835ecf283f32c80fcf5
|
|
Change-Id: Ieede787a13cef79353f13af52488ef3732ac9850
|
|
This is awesome.
- Improve performance by stopping useless string/array conversions.
- Simplify method interface.
- Fix localization bugs - we now know our locale
- Fix bugs with surrogate code points
Bug: 4769095
Change-Id: I8a8ee224b713429ee0a4ce5bd52f1b63378cf56f
|
|
This is a one of groundwork to integrate gesture input.
Change-Id: I5b75c6978b51df91fdc384a9f6d1d5a5ddc563e2
|
|
Bug: 6722052
Change-Id: I92e85b3e49b8f4b228f0cf0994216c5050e0865c
|
|
This will be necessary for uppercasing and titlecasing words
correctly.
Change-Id: I0f446a4c82bc482240ff730a2ad6586a61571d6b
|
|
Change-Id: Ia727ffc2946352bbf79e0c97684f8fa98f428cef
|
|
Change-Id: I9eab910989443704f83711cf4fb0070c5987a13a
|
|
Change-Id: Ib3bfa0a46f5814a6df838005d7243e2f536a98a0
|
|
Bug: 6694141
Change-Id: Ic8fd902554cdf81998f3806a58484d9733848d99
|
|
Change-Id: I2195f365df1799c8b3b2a53670d1df535ab1a742
|
|
Change-Id: Ia837e553ccfe67cd4303096290194a5186df059b
|
|
Change-Id: I4605a571faf5fbc68b18ce525d6019600bfa8cf7
|
|
Change-Id: I267177044c7d7b0d9119839a11057b2bbf41f75f
|
|
Bug: 6252660
Bug: 6166228
Bug: 2704000
Bug: 6225530
Change-Id: I009b54fc2e73cadca6734bdca074d033e81f6a2b
|
|
Bug: 6252660
Bug: 6166228
Bug: 2704000
Bug: 6225530
Change-Id: I7457ac04f8cd4019fb86c986725aae3de1b1a65e
|
|
Bug: 6252660
Bug: 6166228
Bug: 2704000
Bug: 6225530
Change-Id: I919bf70a1213ab5d7c7a9e5715bd72a6e257148b
|
|
It's not used any more.
Change-Id: Id9da40fdbf7078f3ac647d1368237d6601f5a2ba
|
|
Bug: 6252660
Bug: 6166228
Bug: 2704000
Bug: 6225530
Change-Id: Ia54e1e44e1fd4e8ba2c9316928c0595cbe3f933c
|
|
Bug: 6252660
Bug: 6166228
Bug: 2704000
Bug: 6225530
Change-Id: Id923367342a62a650a5f1d38e2fa0e913030dca8
|
|
Change-Id: I86bd7587dd80773a51ba6db312ba55dc41e7c8c7
|
|
Change-Id: Ifd71ce79711b0c15c7764e97351dbb1b8e4c0c2d
|
|
Change-Id: I6ada110a934b0dafc57d0dcd87723275fa733548
|
|
Change-Id: Ia5701d713d0fd5bb646b54a03a1a5602dad0a9e6
|
|
This only returns stuff, but it doesn't change yet how the data
is really passed. It merely adds a way of getting the same data.
Later, the old way will be removed.
Change-Id: If3a064de362175fc5a6781b7a97b65d8730aaf3c
|
|
Bug: 6252660
Bug: 6166228
Bug: 2704000
Bug: 6225530
Change-Id: I8245698fbd170e0f5cbad3c0109774bcaddc0614
|
|
This is only used as temporary storage to be then added to
the other variable, relying on the fact that it is hopefully
sorted. It's better to just add it right away to the final
storage.
Change-Id: I5da702ac9dc579593ab21feb2021a01e5dfdf4dc
|
|
This filtering is already done in native code. It's useless (and
costly) to do it again here.
Change-Id: Ide6794d7a8682a881f097f33e222f10d30f297bd
|
|
This change also checks that the current key is the same key that
started the key repeat, when key repeat timer is fired.
Bug: 6722052
Change-Id: Id69880ded3338a5a3cbe7f8bf951f94f2651119c
|
|
StringUtils.toCodePointArray() had thrown IllegalOutOfBoundsException if
passed an empty string. change to just return an empty int[].
Bug: 6188932
Change-Id: Ic41c628c0d407f49fc98cd48cb7ea13d8d5bdd77
|
|
Bug: 6252660
Bug: 6166228
Bug: 2704000
Bug: 6225530
Change-Id: I5b277124dc9244e78c4a1f4d542a55071eb479bd
|
|
Bug: 6513247
Change-Id: I55e36620bd8b2e7b47a51ccde1b0bf3e277cd56b
|
|
Change-Id: I8b66b0f81300af586db2db3f653ce3e2882a7efe
|
|
Change-Id: Ie741f7f0dccd2aef3ba43ac02776eaac9cb4f9af
|
|
bug: 6714783
Change-Id: Idf674e8e1af80642f2c53f7ae5c03e21c9e04292
|
|
Change-Id: I774a0052038d16677f60f7efa11fd266cb5f3088
|
|
This has a good, although small, impact on performance : it removes
a two-way IPC call in a most frequent case, while possibly adding
one in a rather unfrequent and less critical case.
Also, this fixes a bug with surrogate pairs. This specific branch
of code now correctly handles surrogate pairs.
Aside from this, it should have no impact on behavior.
However, since it does delay access to the previous character in
the text view by a two-way IPC call, it actually goes a long way
toward fixing bug#6668226. It is not really a fix and the race
condition still exists, but this change makes it much, much
harder to hit.
Bug: 6668226
Change-Id: Id11cc6a0b7488d6bd392227cafdcf3a8d4c62f6c
|
|
Bug: 6694141
Change-Id: Ib01575b0994e69ef232a234c575242ec49ed0679
|