diff options
| author | 2024-05-01 17:35:05 -0700 | |
|---|---|---|
| committer | 2024-05-01 17:35:05 -0700 | |
| commit | c95c8f09f5acc494a394725fdafd9ff49136dfd4 (patch) | |
| tree | a58fb822a1f448b11e5f859d0295348777df1847 /libs/input/PointerController.cpp | |
| parent | 8727697ba31725fc3e3ebda984ea026924e74097 (diff) | |
Inline IMMS#setSelectedMethodIdLocked()
This is a follow up CL to our previous CL [1], which introduced
multiple utility methods into InputMethodManagerService with hoping
it'd help us encapsulate things.
Now that we are going to instantiate InputMethodBindingController in a
per-user basis, methods like
@GuardedBy("ImfLock.class")
private void setSelectedMethodIdLocked(
@Nullable String selectedMethodId) {
mBindingController.setSelectedMethodId(selectedMethodId);
}
do not make much sense.
Let's inline this for better readability.
This is a mechanical change thus there must be no observable behavior
change.
[1]: I9cbdd6606f7a44796f6074d0b2e904913bd48e51
67723bf299d79eeb7b88d255ce371f04c926d343
Bug: 325515685
Test: presubmit
Change-Id: I7d55ae9bd428d52dbb9664a79f42d6728a3148f2
Diffstat (limited to 'libs/input/PointerController.cpp')
0 files changed, 0 insertions, 0 deletions