diff options
author | Ben Lin <linben@google.com> | 2020-10-16 17:44:53 -0700 |
---|---|---|
committer | Ben Lin <linben@google.com> | 2020-10-16 17:44:53 -0700 |
commit | 17b79c09b5e5ffc7754cc148a0eabba821db4311 (patch) | |
tree | befdcdcb2bcad66e43634196cdc524a9198afcd1 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
parent | e23a6745d0da53b0f22842c14fc7e9b21e07cda1 (diff) |
PiP: Update DisplayInfo and movement bounds if display is different.
Although there are multiple places to watch out for display change in
PiP, when a task enters PiP, it's possible there has been no display
change, but simply a display addition. That being the case, it's
possible that PiP enters in a secondary display, and so we need to
update all the relevant information of the secondary display.
Bug: 133179171
Test: Enter PiP on a secondary display, default bounds is correct
Change-Id: I3eef2ef5c6b6be99105a876f7e8d43fbba39cbb2
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions