summaryrefslogtreecommitdiff
path: root/rs/java/android/renderscript/ProgramFragmentFixedFunction.java
diff options
context:
space:
mode:
authorBen Lin <linben@google.com>2020-02-19 16:12:48 -0800
committerBen Lin <linben@google.com>2020-03-04 11:59:58 -0800
commit39c9570d459da54aac59a615b9cadd0397383144 (patch)
tree39e9b54b6fac96b25d55accb033d7dcc98629433 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java
parent83f3fb46109791958638a6cb760b1d6eb2fa98e8 (diff)
Track current resized bounds for resized PIP.
Previously, there were only mNormalMovementBounds and mExpandedMovementBounds since these were the only two sizes PIP window can be in (on a per-onMovementBoundsChanged call, that is). With the ability to resize PIP on the horizon, we will need to update the movement bound as it resizes, and also calculcate this movement with the new bound on the fly. Also to make it less confusing, I've renamed: - normalBounds -> minBounds - expandedBounds -> maxBounds Bug: 147361175 Test: Manually. Resize PIP, and then drag around and off-screen, let go - see PIP window snaps back. Resize PIP, tap window (see it expands), and wait for timeout. Restores to previously resized PIP bound. Change-Id: I2ef286d6fa03914a88ac46e2854548548093e79e
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions