diff options
| author | 2021-11-29 14:14:09 +0800 | |
|---|---|---|
| committer | 2021-12-10 04:26:27 +0000 | |
| commit | 7712805752c10330c3748d31b193b83f589f2278 (patch) | |
| tree | b51937dd977d30e25492890d14f4dc065ddbe599 /libs/androidfw/StringPool.cpp | |
| parent | fc8cd1d68f827ab30247b86ca5b32c03c302ec39 (diff) | |
The legacy magnification controller APIs controls only full-screen magnification
See go/b200769372 - the legacy public methods
The legacy magnification controller methods,
setScale(), setCenter(),
getScale(), getCenterX(), getCenterY(),
getMagnificationRegion(),
reset(),
will keep the behavior before that control
only full-screen magnification.
To make the service able to control the actiavted magnifier
on the display, the service should use the new public APIs,
1. setMagnificationConfig(),
2. getMagnificationConfig(),
3. getCurrentMagnificationRegion()
instead of the legacy APIs.
This change
1. Updates the doc of the legcacy APIs.
2. The legacy APIs controls only fullscreen magnification
TODO: Add new public methods, getCurrentMagnificationRegion(),
resetCurrentMagnification() for the current controlling magnifier
Bug: 210069654
Test: atest MagnificationProcessorTest,
atest AbstractAccessibilityServiceConnectionTest,
atest AccessibilityMagnificationTest,
Change-Id: Ia157971d2c9716df7aa14024525ee0adfdc0d46f
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions