diff options
| author | Daniel Eklöf <daniel@ekloef.se> | 2020-07-13 12:19:07 +0000 |
|---|---|---|
| committer | Daniel Eklöf <daniel@ekloef.se> | 2020-07-13 12:19:07 +0000 |
| commit | 3f55cf3d14f0009d2036fec480e1cb7649c34f14 (patch) | |
| tree | 9bf65f6dd8810bd2b56ed4e607a32bca1fe397cd /scripts/benchmark.py | |
| parent | render: doh! flush the last surface damage *outside* of the rendering loop (diff) | |
render: render_margin: don't damage margins when rendering scroll damage
When applying scroll damage, we may have to re-render the
margins.
This is because when we SHM-scroll, we actually move the entire
surface, and thus we end up overwriting the top margin area with old
window content, and scroll in uninitialized memory in the bottom
margin.
But, we don't have to tell the compositor about this - the last frame
always contains correct margins; i.e. there's no change between the
last frame and current frame being rendered.
TODO: we _could_ micro-optimize and only damage the margins after a
surface resize. We do it slightly more often now, when dealing with
state changes in screen flash or scrollback searching. But I don't
think it's worth the effort.
Diffstat (limited to 'scripts/benchmark.py')
0 files changed, 0 insertions, 0 deletions
