| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: 6851364
Change-Id: Ie939a43b8527a76aec213b702d3d850717f22a81
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I03aa6608ee435b36377de41684162b303740f571
|
|/
|
|
| |
Change-Id: I7ba7ac24aa96a0ff19267997c5b58853079bc6dc
|
|
|
|
|
| |
Bug: 6860204
Change-Id: I840b7bf1983ab92fa4e0b180129176539e96409f
|
|
|
|
|
| |
Bug: 6860204
Change-Id: I1e4c03c99415cd9bdea5a8556ff4093c33f0f508
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: 6852483
Change-Id: I873ae0f2e3bc863e989629f8bc0cc90ee33a4920
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Not having a main dictionary is not sufficient reason to display
the hint. If the user already added the word to the dictionary then
we shouldn't be displaying it again, even if we don't have a main
dictionary for the current language.
Bug: 6829798
Change-Id: I6b081f51c82ef395fe2e394fd3167363e743ea6f
|
|/
|
|
| |
Change-Id: I942692bbc2e577482f353d875405c4658a1102fc
|
| |
|
|
|
|
| |
Change-Id: I8f3123b8d727c7beb72e226f80c17794f89c8b60
|
|
|
|
|
|
|
|
|
| |
- also cleaned up RLog menu
multi-project commit with If0fd4fef89d390073e6939d5188ed5696866cb33
Bug: 6188932
Change-Id: I4f66f13bd366b4e8bde742ccd0704f812c6d33f9
|
|
|
|
|
|
|
|
|
|
| |
- new package: com.android.inputmethod.research
multi-project commit with Ic0a5744f3160d13218addd589890623c0d120ffc
Bug: 6188932
Change-Id: Icf8d4a40a5725401799be6e209a640d99a5f34c4
|
|
|
|
|
| |
Bug: 6188932
Change-Id: I692e427ba2e6da7bb15f48208304c4a034392a22
|
|
|
|
|
|
|
| |
This change also removes the reference of SuggestedWords from
GestureTracker and KeyboardActionListener.
Change-Id: I25ef8756007986abf99a931afd665bbfe6fa387f
|
|
|
|
| |
Change-Id: Iee6ae48bb6309c2867b5d2e344fe7d86dfabd654
|
|
|
|
|
|
|
|
| |
showSuggestions is only ever called by updateSuggestionsOrPredictions.
It only feels natural that, when called with a 0-sized or null
suggestion list, it clears the suggestions.
Change-Id: I5b52bc9151afca1bb6c6f0a7f81e3255add92177
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- separate ResearchLog from ResearchLogger
- fix abort menu to explicitly indicate re-enabling of logging
- auto flush entries every 5s
- conform to new suggestedWords class
multi-project change with I9fe1f8fe59d5891daa4ca84af157f36fb1bb17dc
Bug: 6188932
Change-Id: I7e99390f934481c6ed9cea2b259944583edda5bb
|
| |
| |
| |
| | |
Change-Id: I1d1758048649ef337875a5141d825569af7ad38c
|
| |
| |
| |
| |
| |
| |
| |
| | |
Many methods were public but could have been private: change them
to private. Also, add a comment above public methods that don't
come from the IMF to make it clearer why they are necessary.
Change-Id: I574154b015d09c0f8542b81763f497691afdc3c1
|
| |
| |
| |
| |
| |
| |
| | |
We postUpdateSuggestionStrip right away anyway - this only
makes the suggestion strip blink
Change-Id: I2ebd933e9a4c804ef1e8c62ccdaf4953a98a792e
|
| |
| |
| |
| | |
Change-Id: I622503af858ef419e94a17f182253cb03da00462
|
| |
| |
| |
| | |
Change-Id: I417bd5f1318696aaa39fee18f3e750ea5c231f6b
|
|/
|
|
| |
Change-Id: I3ebecec37b49e139c243cf9da8bfe491e7ddada1
|
|
|
|
| |
Change-Id: Id19efc5d279616da52667fa70326b86aba70d4a0
|
|
|
|
| |
Change-Id: I6e7c3aba2b40ecefa483c9680978bc806368e96e
|
|
|
|
|
|
|
| |
If !mWordComposer.isComposingWord(), then mWordComposer.getTypedWord()
will always return an empty string.
Change-Id: Ife66d0abc44c743cbc30d31724e833cda168fd5c
|
|
|
|
| |
Change-Id: Id3765bf9826cc2c7ca70158cda53c75dc58f51c6
|
|
|
|
| |
Change-Id: I7a91d84291bea581ecc8ec5b29b9a87ccec76e7d
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is not exactly the same logically speaking, because it's
theoretically possible that the composing state changed in between
the message enqueueing and it's retrieval. However in the practice,
if the composing state changed the message *must* have been
cancelled and resent, else the behavior breaks. So this actually
is more robust, and removes some obscure requirements on the
calling code.
In the practice, it should also make the cancelUpdateSuggestionStrip
message useless, although this change does not yet remove it.
Change-Id: I75141920ce64e38e2f92e9c02b6c979936eee9a9
|
|
|
|
| |
Change-Id: I2a77e437795fbbea47fd2e604ee6c26f8d0e458a
|
|
|
|
| |
Change-Id: I4b91414190b3786065ebd962a76299b605e5797e
|
|
|
|
| |
Change-Id: Ica9b875d119dea2f8dc237fd63e5b4eaa5e1c400
|
|
|
|
| |
Change-Id: Iff03fe7c4a8eec17c00a2fe99197e0cf21a0630a
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We just resetted the composing state - updating suggestions
is sure to yield no results. We may as well not call
updateSuggestions at all.
We should however still cancel any lingering timer from a
previous input field, to avoid this useless processing.
Change-Id: Ic1a19d577903d792bb797c837cc517ea8d430e75
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I1061da0edfdb05c64c5711717d4ef9fa9681e568
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 6785706
Change-Id: Ic7bf242ef058d116b986d47ad197b6d2802e2342
|
| | |
| | |
| | |
| | | |
Change-Id: I7c16e28ffce4fe0965b756bf2b00ee63b77dd039
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|/
|
|
| |
Change-Id: I606270a0387787445b7cd6b94e4830bfc144b49e
|
|
|
|
|
|
|
|
| |
Just after this, clear() will be called, removing the suggestion
strip from the screen. It will later be displayed again through
onStartInputView, which will update its content.
Change-Id: I15c23ad2adecab76b0791d7fc222d15b6533f3bd
|
|
|
|
| |
Change-Id: I99e912d3edfc7dd3f17ee835331d5fcba976750c
|
|
|
|
|
|
|
|
|
| |
The responsivity is better like this. This does not seem to
feel slow as the previous comment seemed to indicate.
Also remove a stale comment.
Change-Id: I4e7bf9fe28716e112db182e44b3fa88ee4526bb4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After reverting an auto-correct we always have a separator after
the previously inserted word, and the cursor is never touching
a word. Showing predictions is the right thing to do, while
calling postUpdateSuggestions will invariably yield an invariably
blank suggestion strip, which is not very helpful.
Likewise, after we pick a suggestion, we should be showing the
predictions unless showing the addToDictionary hint. There was
a bug here in the corner case that the word would be a candidate
for user dictionary, but the user dictionary provider is not
available: in this case we should be showing predictions, but
we were showing an unhelpful empty suggestion bar.
Change-Id: I287bb5eb4af762bd5a433e85e185fab6d203e91a
|