diff options
author | Yohei Yukawa <yukawa@google.com> | 2018-09-17 16:47:08 -0700 |
---|---|---|
committer | Yohei Yukawa <yukawa@google.com> | 2018-09-17 16:47:08 -0700 |
commit | 484d4afc92cc1a1d58b601f7ad14d63781231b55 (patch) | |
tree | 64e2b7464aeac7829f9ec4f86f9898081771e2d3 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
parent | 7db3ae4f31861edaf1641051530efbbf163907b2 (diff) |
Always use Context.getSystemService() to get IMM
This is a preparation to deprecate the following two methods.
* InputMethodManager#getInstance()
* InputMethodManager#peekInstance()
Since we soon need to stop relying on the current per-process
InputMethodManager singleton model to fully support multi-display,
those two methods really need to be deprecated.
With this CL, framework code no longer depends on
InputMethodManager#peekInstance(), which is also marked as deprecated
in this CL.
InputMethodManager#getInstance() is a bit tricky because it also works
as a constructor of such a per-process singleton instance. Remaining
two call-sites of this method will be migrated in a subsequent CL.
This is a mechanical refactoring, which in theory should have no
observable logical behavior difference.
There could be a small performance regression, but it is basically not
avoidable to correctly support multi-display scenarios.
Bug: 115891476
Test: atest CtsInputMethodTestCases CtsInputMethodServiceHostTestCases
Test: atest CtsWidgetTestCases:android.widget.cts.EditTextTest
Test: atest CtsWidgetTestCases:android.widget.cts.TextViewTest
Test: atest FrameworksCoreTests:com.android.internal.inputmethod
Test: atest FrameworksServicesTests:com.android.server.textservices
Change-Id: I5db31491f3d47d3ad4a621e956995135c72e007b
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions