summaryrefslogtreecommitdiff
path: root/core/java/android/view/InsetsAnimationControlRunner.java
Commit message (Collapse)AuthorAgeFilesLines
* Update the surface position of each control in insets animationTiger Huang2021-05-311-0/+8
| | | | | | | | | | | | | | | If the surface position is changed during the insets animation, the surface position of the controls in the animation should be updated. Otherwise, the cached position in the animation will overwrite the newly-updated leash position. Fix: 177925500 Test: Steps in the bug. Test: 1. Open Window Insets Tests -> Window Insets Controller. 2. Click on the [IME INVISIBLE] button. 3. Click on the [STATUS BARS VISIBLE] button during IME animation. See if the position of IME (Gborad) is correct. Change-Id: I7441426a41019996651220e86ca90dd416ef9498
* Force showing navigation bar while IME is visibleTiger Huang2021-05-171-1/+12
| | | | | | | | | | | | | This CL revokes navigation bar control to make navigation bar visible while IME is showing, so the button to dismiss IME would be available. This CL also lets IME receive visible navigation bar insets, regardless of the navigation bar visibility. Fix: 167971834 Fix: 186789472 Test: atest WindowStateTests WindowInsetsControllerTests Change-Id: I2e723d4fc50d006127caa473d67c2f6af0d2cbcd
* Add proto-based client side dumping for IME tracingAnmol Gupta2020-09-291-0/+11
| | | | | | | | | | | | | | | | This CL implements a mechanism to dump IME related client states into a proto file which can later be imported to winscope to allow easy debugging. A new abstract class ImeTracing.java declares the methods related to scheduling, collecting and dumping logs. Two child class implement these methods for server and client separately. The Design Doc for the IME tracing project is: go/ime-tracing Bug: 154348613 Test: start trace by calling "adb shell ime tracing start" end trace by calling "adb shell ime tracing stop" pull trace using "adb pull /data/misc/wmtrace/ime_trace.pb ime_trace.pb" Change-Id: Ia89f11d5ef8a220ea7746191b18769cea5a8359d
* Use separate thread if app doesn't listen to animationsJorim Jaggi2020-03-111-0/+56
There is no need to introduce jank risk and run the inset animations on the main thread if the app doesn't listen to animation events. In that case, move the animations onto a separate thread. Bug: 118118435 Test: Inspect systrace Change-Id: Ib6e4b4ce8e9dd8e27761ced6eb8d7700b6236a32