This issue is caused by three reasons.
- In touch move event and while time debouncing is going on, wrong key
is shown as pop-up preview.
- There is no pop-up preview key shown when touch up event occurs and
also showing pop-up preview message is unintentionally canceled.
- In detectAndSendKey() method, nearby keys' primary codes are
mistakenly sent as Key codes.
This is the last of three changes to fix bug #2868304
Bug: 2868304
Change-Id: Ie482167b2ae2804fa1aa43ffb5067af47b7553f1
- retrieve bigrams that only starts with character typed and neighbor keys
- contacts bigram
- performance measure
bug: 2873133
Change-Id: If97c005b18c82f3fafef50009dd2dfd972b0ab8f
When key is pressed, each key will have a halo which is 0.05 inch
wider than the key.
Bug: bug2517112
Change-Id: I1368ff4af5f5d230b8c2f0c05c3c27bdb89027ae
In makeKeyboards(), there is a fall through pass in which the
keyboards' id (mSymbolsId and mSymbolsShiftedId) will not be updated.
Then in toggleShift(), current keyboard id (mCurrentId) will not match
any of two and nothing happens.
Bug: 2825858
Change-Id: Iaf8a7368f513b35cf77a67794ecd3e21aa08484b
This change will parse the voice-search word-based
alternatives from the bundle returned by the server,
rather than generating them on the client.
Change-Id: I7d7abc224de3ab8f37eca18632a427d39fd61a78
- Rename the jni library name
- Revert the local cert
- LatinIme2Google -> LatinIME
Please note that we'll use the new package name: com.google.android.inputmethod.latin
Change-Id: Ibbab07e8102ade5a93660c0723cd86f600c14a7d
Disable until we find a cleaner solution to highlighting for correction (may need
a framework change).
Removed a check for VoiceInput.DELETE_SYMBOL, which is not in use any more.
- after first character, only suggests bigram data (but doesn't autocomplete)
- after second character, words from dictionary gets rearranged by using bigram
- compatible with old dictionary
- added preference option to disable bigram
Change-Id: Ia8f4e8fa55e797e86d858fd499887cd396388411
- Fixed caching of words - some StringBuilders were being recycled while also being cached. Making copies now.
- Fixed regression in revert - don't reset the word composer after saving the accepted word.
- Removed flicker when cursoring through a word - delay the abortCorrection() until we need to and do the correction
as an atomic operation.
- Fixed replacing of "selected" words (double-tap to select a word)
Still to do:
- Remove flicker on highlighting a word - may need a framework change
- Don't remove spans on text that's already in the text field - may require a framework change.
- Figure out what to do about the punctuations that share the suggestion strip when in correction mode.
