Do not record log split time when handling separator
Previously handleSeparator() caused the ResearchLogger to mark the time at which a LogUnit should be broken. However, this causes the motion data associated with a separator to be associated with the LogUnit of the previous word. This change corrects this bug. Change-Id: I8b4d4fa6de2a013de9e2a28bb668c446a07f1957
This commit is contained in:
parent
54c091d284
commit
636b8c4231
1 changed files with 0 additions and 1 deletions
|
@ -1905,7 +1905,6 @@ public final class LatinIME extends InputMethodService implements KeyboardAction
|
||||||
private boolean handleSeparator(final int primaryCode, final int x, final int y,
|
private boolean handleSeparator(final int primaryCode, final int x, final int y,
|
||||||
final int spaceState) {
|
final int spaceState) {
|
||||||
if (ProductionFlag.USES_DEVELOPMENT_ONLY_DIAGNOSTICS) {
|
if (ProductionFlag.USES_DEVELOPMENT_ONLY_DIAGNOSTICS) {
|
||||||
ResearchLogger.recordTimeForLogUnitSplit();
|
|
||||||
ResearchLogger.latinIME_handleSeparator(primaryCode, mWordComposer.isComposingWord());
|
ResearchLogger.latinIME_handleSeparator(primaryCode, mWordComposer.isComposingWord());
|
||||||
}
|
}
|
||||||
boolean didAutoCorrect = false;
|
boolean didAutoCorrect = false;
|
||||||
|
|
Loading…
Reference in a new issue