summaryrefslogtreecommitdiff
path: root/libs/androidfw/StringPool.cpp
diff options
context:
space:
mode:
author Yohei Yukawa <yukawa@google.com> 2022-10-28 06:52:25 -0700
committer Yohei Yukawa <yukawa@google.com> 2022-10-28 06:52:25 -0700
commit191ca0b4e0426882949797975af89168e1e5eee8 (patch)
treed308111b0ab0c5862f27d546e5f44b8fbe93c88b /libs/androidfw/StringPool.cpp
parent7a5652f7b1c6d060785e1f68645c336d44a1138e (diff)
Add InputMethodSubtypeHandle (again)
This CL introduces InputMethodSubtypeHandle which is similar to what we used to have in the past [1]. In the previous attempt, com.android.server.input.PersistentDataStore saved the data into the storage in the following format. <keyboard-layout descriptor="..." input-method-id="com.android.testime/.Ime1" input-method-subtype-id="1" ... /> While the new format is going to be something as follows, in general InputMethodSubtypeHandle enables you to treat the actual String object as an opaque byte data by providing both decode/encode methods with data validation. <keyboard-layout descriptor="..." input-method-subtype-handle="com.android.testime/.Ime1:subtype:1" ... /> In addition to decode/encode methods, InputMethodSubtypeHandle provides several useful functionality such as Parcel support and methods like getComponentName(). See test cases for details. [1]: Ie88ce1ab77dbfe03ab51d89c1dc9e0a7ddbb3216 d5f7ed9fe9dc3590f6ef9cb7470e29e836a95907 Bug: 252816846 Test: atest FrameworksCoreTests:InputMethodSubtypeHandleTest Change-Id: I5b052fba64f8036e7dd874c34b81f5fd4ffeaca3
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions