diff options
| author | Daniel Eklöf <daniel@ekloef.se> | 2025-01-02 08:08:24 +0000 |
|---|---|---|
| committer | Daniel Eklöf <daniel@ekloef.se> | 2025-01-02 08:10:51 +0000 |
| commit | 56d2c3e990509d18de31e6009e0d0c6254f99b67 (patch) | |
| tree | fa79862424f122da23e68816a0713b502406f7ac /debug.c | |
| parent | term: limit app-id to 2048 characters (diff) | |
config: don't allow colors.flash-alpha to be 1.0
A compositor will not send a frame callback for our main window if it
is fully occluded (for example, by a fully opaque overlay...). This
causes the overlay to stuck.
For regular buffers, it _should_ be enough to *not* hint the
compositor it's opaque. But at least some compositor special cases
single-pixel buffers, and actually look at their pixel value.
Thus, we have two options: implement frame callback handling for the
overlay sub-surface, or ensure we don't use a fully opaque
surface. Since no overlays are fully opaque by default, and the flash
surface is the only one that can be configured to be
opaque (colors.flash-alpha), and since adding frame callback handling
adds a lot of boilerplate code... let's go with the simpler solution
of
Diffstat (limited to 'debug.c')
0 files changed, 0 insertions, 0 deletions
