tree c31b27bb3ad1262853566107ae4a166a9648dd20
parent 5e46a66c6d3647822de808e9265b1813b6c4bade
author Yohei Yukawa <yukawa@google.com> 1541010812 -0700
committer Yohei Yukawa <yukawa@google.com> 1541051801 -0700

Extract IMM internal flags into StartInputFlags

This is a mechanical refactoring like we did to split
InputMethodClient for Bug 118040692.

So-called "controlFlags" in InputMethodManager (IMM) was originally
introduced for IMM#startInput()/windowGainedFocus() [1] to carry
additional client information then reused when we unify startInput()
and windowGainedFocus() into startInputOrWindowGainedFocus() [2].

This CL mechanically moves the location where those flags are defined,
from InputMethodManager.java to a newly created file
StartInputFlags.java.

This is still just a mechanical refacotring / renaming.  There should
be no user-visible behavior change.

 [1]: Icb58bef75ef4bf9979f3e2ba88cea20db2e2c3fb
      7663d80f6b6fd6ca7a736c3802013a09c0abdeb9
 [2]: I56934f18e30d90fcdf77bcbb0c35a92a5feb1b82
      05c25f8a3a033816ac25aa5cd7db5b1ab495bc3f

Test: atest CtsInputMethodTestCases CtsInputMethodServiceHostTestCases
Test: atest FrameworksCoreTests:com.android.internal.inputmethod.InputMethodDebugTest
Change-Id: If5a4810dece852edcff0d1119463711249bb7ef2