diff options
| author | Daniel Eklöf <daniel@ekloef.se> | 2022-09-22 16:39:00 +0000 |
|---|---|---|
| committer | Daniel Eklöf <daniel@ekloef.se> | 2022-09-23 18:33:02 +0000 |
| commit | 3be44fb316b166c0b5d5536fdb5bb6c7abdd3a90 (patch) | |
| tree | 2cca9ab228f706ad2ac443b0bfaee9003615951a /scripts/benchmark.py | |
| parent | render: fix application of old scroll damage when double buffering (diff) | |
render: overlay: fix visual glitches when double buffering
When rendering the overlay for scrollback search, the logic assumed
buffer re-use. On some compositors this isn’t happening (on
e.g. KDE/plasma we’re forced to double buffer).
This resulted in matches not being highlighted correctly.
The problem is in how we calculated the region for which areas to
clear ("un-dim"). It uses the "previous frame’s see-through area"
minus the current frame’s see-through area.
However, when we’ve detected that the current buffer isn’t the same as
the last one, we set the last frame’s see-through region to "the
entire buffer". Thus, when calculating the diff, we end up with an
empty region, and nothing is highlighted.
Fix by simply using the current frame’s see-through region as-is when
we’ve detected we’re not re-using the last frame’s buffer.
Diffstat (limited to 'scripts/benchmark.py')
0 files changed, 0 insertions, 0 deletions
