Jean Chalard 3b4c1d3056 Change a heuristic and add a log.
The heuristic in RichInputConnection makes little sense
when textLength > mExpectedSelStart but we have
more than 1024 characters of text. If there are that many,
it's about 100% sure that 1024 is not the correct cursor
position. With no good guess, we'll just continue trusting
the app, even though we know it's lying : at least it will
make the problem visible to the app author.

Also, there have been a lot of confusion about initialSelStart
and initialSelEnd. The keyboard should log them so that
it helps us and editor authors debug more easily these
common problems.

Issue  in AOSP and
Bug: 12772035
Change-Id: I6665a16c9f2832d33ee323f033bb38bcc092a3b4
2014-02-20 23:49:20 +09:00
2014-01-14 10:37:15 +09:00
2014-02-20 23:49:20 +09:00
Description
A mirror for futokb (https://gitlab.futo.org/keyboard)
681 MiB
Languages
Java 43.9%
C++ 33.2%
C 11.7%
Kotlin 10.6%
Makefile 0.2%
Other 0.2%