diff options
author | Yohei Yukawa <yukawa@google.com> | 2015-05-19 22:15:02 -0700 |
---|---|---|
committer | Yohei Yukawa <yukawa@google.com> | 2015-05-19 23:21:17 -0700 |
commit | 54d512c9acc44484b7baa8d8cf02067d175dde11 (patch) | |
tree | f3ba3230b94bac2b22d21124df43efd61f9cfc95 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
parent | 1c5bf7f1ddc8c9c9844a1bc1a7e4ce53dcc5d5bd (diff) |
Invalidate IMMS#mCurrentSubtype when upgrading the current IME.
Whenever the package to which the current IME belongs is
modified, IMMS#mCurrentSubtype needs to be invalidated.
Otherwize, InputMethodManager#getCurrentInputMethodSubtype()
continues to return the previously selected subtype.
One example scenario would be to update metadata of a subtype
in a new version of an IME with keeping the same subtypeId.
Suppose imeSubtypeExtraValue was updated from "ABC" to "XYZ".
In this scenario, the subtype in question retrieved with
IMM#getInputMethodList() then InputMethodInfo#getSubtypeAt()
has imeSubtypeExtraValue "XYZ", while the subtype returned
from InputMethodManager#getCurrentInputMethodSubtype() still
has imeSubtypeExtraValue "ABC".
With this CL, IMMS#mCurrentSubtype will be invalidate when
the active IME package is modified.
Bug: 21310194
Bug: 20708002
Change-Id: Ifbb35034d9c8e477ebb5353d2a470dfc1627bbd5
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions