summaryrefslogtreecommitdiff
path: root/core/java/android/window/PictureInPictureSurfaceTransaction.java
Commit message (Collapse)AuthorAgeFilesLines
* Add flag to explicitly set setCanAffectSystemUiFlagsHongwei Wang2022-06-101-2/+21
| | | | | | | | | | | | | | Within the PictureInPictureSurfaceTransaction class, one can explicitly express the intention to call Task#setCanAffectSystemUiFlags(false) and it is typically used if an Activity is entering PiP. Video: http://recall/-/b1EZhgUkQcpML5OwZekLBN/dlG6qSf9pT2f4YlIe2Klb3 Video: http://recall/-/b1EZhgUkQcpML5OwZekLBN/cfXwlpol5vi2AER32rKu2x Bug: 213598210 Test: 1. follow the reproduce steps in the bug. \ 2. make sure PiP from split-screen has no regressions. \ see also the videos. Change-Id: I7c4624a89ff812f874270fe0092617328b557393
* Handle PiP shadow radius in WMShellHongwei Wang2022-03-281-4/+26
| | | | | | | | Deprecate also the shadow radius for PiP in Task Bug: 206508708 Test: Verify the PiP enter/exit/move/resize transitions Change-Id: I8ff83dd4e626a3455373fed6c908cf131ecae8fe
* Fix the transition from Split to PiPHongwei Wang2021-12-091-29/+89
| | | | | | | | | | | | | | | | - Do not bring split to top on entering PiP When swiping up to home (or other cases) triggers one of the split-screen children enters PiP, do not try to bring the other task to top since the pair should be considered invisible. - When entering PiP from split screen or non-auto PiP case, use the alpha information in PictureInPictureSurfaceTransaction to hide the task which would later be turned back on to avoid flicker. Bug: 190855091 Bug: 205894095 Video: http://recall/-/aaaaaabFQoRHlzixHdtY/42RWtayanp2qG0mHSf4Q5 Test: manual, enter PiP from split-screen, see Video Change-Id: I1559748cd583c20d79ee458822d66e7801733d3a
* Pass the float9 values in PictureInPictureSurfaceTransactionHongwei Wang2021-05-071-26/+21
| | | | | | | | | | | For auto enter PiP from landscape when no source rect hint is specified, we should actually use the skew instead scale values to set the matrix transform. Video: http://recall/-/aaaaaabFQoRHlzixHdtY/dpLVOQzIVjdJpn5kg7T4Fc Bug: 179720719 Test: manual use ApiDemos app, see video Change-Id: Ic7072e8354329584f9cb75876911c3d58d78e7f5
* Apply PictureInPictureSurfaceTransaction upon reparentHongwei Wang2021-04-221-0/+19
| | | | | | | | | | | | | | | | | | When autoEnterPip from Task with multiple activities, besides passing the mLastRecentsAnimationBounds we should also try to pass the last PictureInPictureSurfaceTransaction to the new Task and apply both. Changed also - deprecate the last recents animation bounds and use the transaction only - reset the transform once applied to the original task Known issue: original task appears transparent in overview once. Video: http://recall/-/aaaaaabFQoRHlzixHdtY/hNZ0H62PqgVDEUGh1TVMiT Bug: 184789412 Bug: 185509920 Test: manual with ApiDemos, see Video Change-Id: I7fb77e41e1963e14ecaf53bd135d6b4cb24493c9
* Apply the whole auto pip transaction in recents animationHongwei Wang2021-03-251-0/+140
Take the full transaction details passed from Launcher, including position / windowCrop / scale / roundRadius and apply them in RecentsAnimationController.TaskAnimationAdapter#onCleanup to make sure the final state of autoEnterPip transition can be carried over. Note: there are still several frames off when entering PiP from landscape with autoEnterPip being enabled. Bug: 179720719 Test: manually using the ApiDemos app Change-Id: Ibfff75e09943960cfcd816d6c52a80d7a8af8fe8
generated by cgit v1.2.3 (git 2.25.1) at 2025-12-22 07:10:42 +0000