This is a followup for comment in I77bf8c844838f32888004611975cfa316255961b
lastClientId doesn't need to be static as MultiClientInputMethod is single instance.
Bug: 128751901
Test: Manually verified using steps in bug.
Change-Id: I049a5e9966408b1d304e23713fae2c3597d89a5c
MSIME sample can now set connection active/inactive.
Bug: 128751901
Test: Manually verified using steps in bug.
Change-Id: I77bf8c844838f32888004611975cfa316255961b
Otherwise SDK build will fail because this target puts artifacts to
privileged app dir, which is not expected for samples in the SDK
build.
You can still build MultiClientInputMethod on command line by
explicitly specifying this in the build target.
Bug: 115784148
Test: locally verified as follows:
lunch sdk_phone_armv7-userdebug
make -j PRODUCT-sdk_phone_armv7-sdk
Change-Id: I09282fa39d13f8078881a3b215cad7d3c0e81486
This CL adds a sample multi-client IME. Ahthough there are still many
limitations and missing features in this sample IME, this CL
demonstrates how a multi-client IME can be implemented.
Fix: 115784148
Test: prebuilts/checkstyle/checkstyle.py -f \
development/samples/MultiClientInputMethod/
Test: Manually verified as follows:
1. make -j MultiClientInputMethod
2. adb install -r $OUT/system/priv-app/MultiClientInputMethod/MultiClientInputMethod.apk
3. adb root
4. adb shell setprop persist.debug.multi_client_ime \
com.example.android.multiclientinputmethod/.MultiClientInputMethod
5. adb reboot
6. Try multiple text input scenario
Change-Id: Ide43e16448fa00355a2c08bc45ae94d98553da50
