Remove useless code (A63)
If the separator is not a space, then we will always call setPunctuationSuggestions and reset the suggestion strip anyway. If the separator is a space, then the cursor has a space on the left, which means isCursorTouchingWord depends only on whether it touches a word on the right. If we were displaying the "add to dictionary hint", it means a suggestion was just chosen, so it had to be displayed, and that requires a composing word and no non-separator at the right of the cursor. In the end, if we go through this postUpdateSuggestions call, we are sure we will reset the suggestions later in this method, either by calling postUpdateBigramPredictions, or setPunctuationSuggestions. Change-Id: I95d5f77a5d0ac6d1a6ced8d67d6ac8f650db4a32
This commit is contained in:
parent
8ba33c1a49
commit
43193ad60f
1 changed files with 0 additions and 5 deletions
|
@ -1534,11 +1534,6 @@ public class LatinIME extends InputMethodService implements KeyboardActionListen
|
|||
// Returns true if we did an autocorrection, false otherwise.
|
||||
private boolean handleSeparator(final int primaryCode, final int x, final int y,
|
||||
final int spaceState) {
|
||||
// Should dismiss the "Touch again to save" message when handling separator
|
||||
if (mSuggestionsView != null && mSuggestionsView.dismissAddToDictionaryHint()) {
|
||||
mHandler.postUpdateSuggestions();
|
||||
}
|
||||
|
||||
boolean didAutoCorrect = false;
|
||||
// Handle separator
|
||||
if (mWordComposer.isComposingWord()) {
|
||||
|
|
Loading…
Reference in a new issue