| Commit message (Collapse) | Author | Files | Lines |
|
- 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: I0376c38451de66ff8c40b488ed3a8599326755ad
Auto-generated-cl: translation import
|
|
Change-Id: Iff0a0e8835f4d630b51a15c0d91881437094e785
|
|
Moved from jb-dev branch (I807fd6f4).
Bug: 6722867
Change-Id: I9764ac72f726396caaac819675d440372c882981
|
|
Change-Id: I3c85a80610fde664a328f5606d0724f00d445ebe
|
|
Change-Id: I4da3c976838e8eb56c9ec80aafaaf54d759b7981
|
|
Change-Id: I1d1758048649ef337875a5141d825569af7ad38c
|
|
Change-Id: I5435cef8ac6be523934ffa394952cb120c8e89d6
|
|
This will de-duplicate a lot of existing code.
Change-Id: Idaffb2fde23b9741f057bcb2ecb3dde9d12ea5c5
|
|
Change-Id: I29d6afbcba0998558c9b19287a460d9f0e410994
|
|
Why was this copy-pasted :(
Change-Id: I6a537c56425ad039d7301a5fe1e0485784f07914
|
|
Change-Id: I5f4a18e43f3012acf96978d625325bf7c69c9c80
|
|
Change-Id: I5d79021e69cc738e3013e31764ab0a59e15decdf
|
|
Change-Id: I9df5cf95c14da2e11ac709ca5e32dc7db3b02c37
|
|
Use the word the same way for suggestion and prediction. It makes
little logical sense that the trailing single quotes be removed
for suggestion lookup but not for prediction lookup.
Change-Id: I0de4b5f7c5b4c1b4ba1817ff9653d7c03967146d
|
|
Avoid special casing the whitelist dictionary by having it implement
the interface it pretends it implements
Change-Id: I8b873cb0f3fe13cefd32c8cb756a25c8ae16a2b4
|
|
The user history dictionary should be the one knowing it does not suggest words
beyond 2 characters, not Suggest.
Change-Id: Ie85ec6116eb495e0c7f51108e4620c5ae536f4bf
|
|
Bug: 6788235
Change-Id: I5a4212872e0fd3f9e80168fd3abd5c2b3bc4110f
|
|
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
|
|
Bug: 6789576
Change-Id: Ia768258f6fa121c7a7757093eb8a20e665580865
|
|
We postUpdateSuggestionStrip right away anyway - this only
makes the suggestion strip blink
Change-Id: I2ebd933e9a4c804ef1e8c62ccdaf4953a98a792e
|
|
Change-Id: I622503af858ef419e94a17f182253cb03da00462
|
|
Bug: 6789576
Change-Id: I6de1e1aa64cf14f38ecb250579418bc518f0d838
|
|
Bug: 6789576
Change-Id: I7c55d36afad7ef6046353b3c9e849a54a6dc83ae
|
|
Change-Id: I417bd5f1318696aaa39fee18f3e750ea5c231f6b
|
|
Change-Id: I3ebecec37b49e139c243cf9da8bfe491e7ddada1
|
|
Change-Id: Id568adac98135cffceb111000e80f77928c045ea
|
|
Change-Id: Id83b34e076ef91e06d7c1dd2b3ee7bb64d01b8cb
|
|
bug: 6790620
Change-Id: I6fd271c6f79790cfb9d875b052854eab60a30b7f
|
|
It's in a full build or just an unbundled build.
Bug: 6790620
Change-Id: Ifa2df86462747acb8b561ebab879e03b1201b4f7
|
|
Change-Id: I48fd690e9368a6637c7fa93c15b6ecadcbe47ce8
Auto-generated-cl: translation import
|
|
Change-Id: Ib4afefac0e87c814c9e54cb65e78ee584c3f954c
|
|
Change-Id: Id2b0e242f7e9ce0ca888067857f8b64c02fde84e
|
|
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
|
|
Change-Id: I588d7acc6f64360404440ad8dc2c00296046b09d
|
|
Change-Id: I46c6a6e1c1536599cb909bf81297001b238f2ec8
|
|
Change-Id: I1061da0edfdb05c64c5711717d4ef9fa9681e568
|
|
Bug: 6785706
Change-Id: Ic7bf242ef058d116b986d47ad197b6d2802e2342
|
|
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: 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
|