summaryrefslogtreecommitdiff
path: root/libs/gui/BufferQueueThreadState.cpp
diff options
context:
space:
mode:
author Lloyd Pique <lpique@google.com> 2020-01-21 15:26:18 -0800
committer Lloyd Pique <lpique@google.com> 2020-01-29 11:49:09 -0800
commite8fe47480acb765e8d33549c7b08d8561f7db982 (patch)
tree77c2fdb2aa0dd39422fdb2f98a6e36114de47403 /libs/gui/BufferQueueThreadState.cpp
parent5e18e87382e421c37947f92096832d589afbf8af (diff)
CE: Use distinct source and destination clip rectangles
The existing logic used a single clip rectangle, which was passed to RenderEngine as both DisplaySettings.physicalDisplay and DisplaySettings.clip. In at least the GLES backend, the first is used to set the GL viewport, and the later is used to set the clip rectangle. However if an Output is set up to render an arbitrary subrectangle of a larger physical display space, distinct values need to be used -- typically the viewport (destination clip) is set to (0, 0, w, h), while the source clip is set to some (x0, y0, x0 + w, y0 + w). Note that in particular we still need to both rectangles to the same (0, y0, w, y0 + h) rectangle when the goal is to hide a notch on a physical device, so the rectangle settings must be obtained from code outside of libcompositionengine. Test: go/wm-smoke on crosshatch, checking notch-hiding Test: atest libcompositionengine_test Test: CtsColorModeTestCases Test: CtsDisplayTestCases Test: CtsGraphicsTestCases Test: CtsUiRenderingTestCases Test: CtsViewTestCases Test: android.media.cts.EncodeVirtualDisplayWithCompositionTest Bug: 144116549 Change-Id: Ic7218da2457f2645af180a1b4eed3dd6896db7d1
Diffstat (limited to 'libs/gui/BufferQueueThreadState.cpp')
0 files changed, 0 insertions, 0 deletions