| Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I4c576a0b0b632cdf413f2ccd5c69dbd37747fbd3
|
|
This is follow up change of If4b82376
Change-Id: I9b0d86ba630011372f41f26efb56bb0a80e09505
|
|
Change-Id: I04e691fbc9227d4df195429bca89edea93575347
|
|
Change-Id: Id33998e2a99be9249de4011892555f10c5d0968d
|
|
Change-Id: I98238359dffd76a620d3b0e73b3b22dd82c56c93
|
|
Change-Id: If4b823768ab9c073625da3034ecc8091be1df230
|
|
Change-Id: I280b1fa6a018e095e9b36ea5475dde68e0965350
|
|
This change fixes Gingerbread theme.
Change-Id: I142437ac0173df48ab36390f47ed67c6cea24a65
|
|
Change-Id: Iad756a7a775c93f3344c6962e7b3456ef8339490
|
|
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
|
|
Change-Id: Ie93c7437fb9a3fe63adaa48c2d4a723f96c0a0e1
|
|
Change-Id: I152df7b876a1756b69ded2ca4fb3ee26b38c971f
|
|
Change-Id: I4894d188d5612380cc9f8eec7cb72544e37fb2b0
|
|
Before
==== test finished, terminate logcat =====
(0) 121.97 (0.28%)
(1) 42032.07 (95.46%)
(2) 11.03 (0.03%)
(3) 12.19 (0.03%)
(4) 10.02 (0.02%)
(5) 1417.41 (3.22%)
(6) 258.43 (0.59%)
(20) 50.20 (0.11%)
Total 44033.07 (sum of others 43913.32)
After
==== test finished, terminate logcat =====
(0) 110.81 (0.29%)
(1) 36416.11 (94.47%)
(2) 10.06 (0.03%)
(3) 9.45 (0.02%)
(4) 9.83 (0.03%)
(5) 1535.52 (3.98%)
(6) 290.25 (0.75%)
(20) 40.57 (0.11%)
Total 38546.83 (sum of others 38422.60)
Change-Id: Iffd24ce0b2dc422c8c6085d5be5f6bfdaf59ca7d
|
|
+1 1
-1 2
+2 0
-2 0
+3 0
-3 0
+4 6
-4 1
+5 4
-5 3
+6 3
-6 10
+7 7
-7 5
Before:
Total 42936.28 (sum of others 42814.63)
After:
Total 40860.56 (sum of others 40733.92)
Change-Id: I6a3d52f31ec181970083358280c3ebaca0a1f63e
|
|
Bug: 5759096
Change-Id: I1e1250d917e726e1931de3247ddc782b005ab5c1
|
|
Bug: 5759092
Change-Id: I328e2043075ce5d0d0285febc4a9b7356702c250
|
|
Change-Id: Ie288272bc75832db7d743262c4c4fbe73b6dca04
|
|
Change-Id: Id737d943d20e3de3db568162caf40d3e956c7fae
|
|
Change-Id: I101b6927d43e86b3c636c1a527e181df8af9c73e
|
|
Change-Id: I70919ff30622afa1d8c29ca45589fa617f2c1f0e
|
|
Change-Id: I724df0be7ac07ffb9f1f4974175aed5a2606221b
|
|
Change-Id: I5fd8f6ac0f42152fb0e2aaaedc6092f6d82fe677
|
|
Also rename the function to reflect better the behavior.
An upcoming change will clean up the remnants
Change-Id: I19bdf0d9e95f62ee749e1f64fe17132c4a5ef0bc
|
|
Change-Id: Ibea64133f200dce80034c641d4798b62843a2512
|
|
Bug: 5759096
Change-Id: Ie1f1800d0f32ac0938715c79974e0f382c9c3d27
|
|
Small simplification of the code.
Change-Id: I1f67ae529bbb2c9316bf5e083d367c57040ea22c
|
|
Change-Id: Ie0d1204e94fcdf9d578974256bf2ae3e87797f13
|
|
This change introduces KeyboardSet and SubKeyboard XML definitions to
represent a set of keyboard layouts.
Bug: 5002108
Bug: 5679585
Change-Id: Ib6c8d5936187381bb6725c9fe574e93871c01a86
|
|
Upon autocorrection, there is visual feedback in the text
view that quickly flashes the background of the text that
just changed. This fixes a race condition that happens
upon autocorrection when typing fast, and that results in
flashing one character too far left (typically, the flashing
area includes the whitespace before the corrected word and
not the last character of the corrected word).
This happens because the call to commitCorrection may
happen before or after the IPC sent by sendKeyChar, but the
arguments are fit only for the case where it arrives first.
Change-Id: I9b5442a665aad5a9bc66cd49228075b9056b37fa
|
|
Bug: 5722703
Change-Id: I56bcf6ccde82b4176093de4f197a8736b0cc8c10
|
|
Change-Id: I95f09da03457933a14b549e04575d566de97dd49
|
|
This place is very confusing because a member variable with
a consistent meaning is hijacked for the duration of a function
to mean something else. This is in the way of easy-to-understand
refactoring.
Change-Id: If79bc771950d6bfc0ad5f0e9c51c7ef1dbb45b66
|
|
- Stop the word composer from escaping - take a page from the law
of Demeter and only report what is actually needed.
- Fix typos in comments.
- Add a comment for a fishy processing.
- Remove a useless local variable.
Change-Id: I5fa78901cbb5483fc9683bfb7094f47244b85df6
|
|
Change-Id: I0f62ce8a6a4d2b6134db698f8b8d0576616e524d
|
|
Change-Id: I3d376dfda3acd8864274390de3ff5752b18456e0
|
|
mBestWord has a confusing name - it's actually an auto-correction.
It's cleaner if it lives in the word composer because an
auto-correction should be tied to a specific user input, and
should be reset each time the user input changes to avoid
race conditions.
Change-Id: I718d29395bc747372067e6440e090c6a181994ae
|
|
This change moves
* KeyboardSwitcher.getKeyboardId to KeyboardSet.<init> and
KeyboardSet.getKeyboardId.
* KeyboardSwitcher.getF2KeyMode to KeyboardSet.
This is the first step to get rid of shift state from Keyboard.
Bug: 5002108
Bug: 5679585
Change-Id: I2a5a97e5e89277bc606916d45c1afbc8d105d773
|
|
Change-Id: I4393ff1ec28a6b3118d1344dd6d82d04899dea42
|
|
Instead of ignoring silently a found bug, throw an exception.
Change-Id: I0aa96d0cab022b6a5e7cffe8a592dcc443c3c7a8
|
|
Change-Id: Icc58ccea1178d9f35f5be0dceebab67bbb965b7f
|
|
Change-Id: I032fc50a62a573ba4258530e695c8c88467783c6
|
|
Change-Id: Iefe10e94e2d88171387351a5b6cab52e281d0f76
|
|
+1 2
-6 2
Performance
before
==== test finished, terminate logcat =====
(0) 100.34 (0.26%)
(1) 37149.26 (95.30%)
(2) 8.43 (0.02%)
(3) 11.18 (0.03%)
(4) 9.92 (0.03%)
(5) 1330.60 (3.41%)
(6) 250.46 (0.64%)
(20) 12.41 (0.03%)
Total 38982.50 (sum of others 38872.59)
after
==== test finished, terminate logcat =====
(0) 97.65 (0.26%)
(1) 35427.43 (95.32%)
(2) 10.30 (0.03%)
(3) 8.95 (0.02%)
(4) 11.01 (0.03%)
(5) 1224.67 (3.30%)
(6) 243.76 (0.66%)
(20) 40.91 (0.11%)
Total 37167.04 (sum of others 37064.68)
Change-Id: Id4d3b88a9cdef765affc52973aeac951ecc6a8ca
|
|
Both tests have the same meaning. They should be merged.
Also, if "deleteLast()" deletes more than one char (which
never happens in the current implementation, but it's not
guaranteed), the new code is more correct.
Change-Id: I216df7cd45f4a7d76d1d5d6aa7f8d7f9a6e35ea3
|
|
If mHasUncommittedTypedChars is true, then
mWordSavedForAutoCorrectCancellation must always be null, and
spaceState must always be SPACE_STATE_NONE.
Hence, this change is supposed to be very no-op.
Change-Id: I2716f7372d996cc4dec40a4b7ac1ee7f5f4afe91
|
|
postUpdateShiftKeyState used to be called also when
mEnteredText is not null => this is a bugfix.
The rest does not change the logic, as posting a message can
be done anywhere within the function with no impact.
Change-Id: I7888797c0778702d64f96701e35b611a55a6a259
|
|
Change-Id: I57b2232f7fde32df5f6e1925aad1df988def34f9
|
|
Change-Id: Iec19af98209e1ea8ecd176d3be04d628d4b38950
|
|
If there are no uncommitted chars, we shouldn't enter any of
the tests that follow. We didn't use to, but a change today
made it possible - it should not happen.
There is no point in doing the rest of the tests, they are
sure to fail.
Change-Id: I580dd104aff3585de72a93b38989bfd9713f615b
|