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
This commit is contained in:
Daniel Eklöf 2025-01-02 09:08:24 +01:00
parent c7ab7b3539
commit 56d2c3e990
No known key found for this signature in database
GPG key ID: 5BBD4992C116573F
3 changed files with 26 additions and 2 deletions

View file

@ -62,6 +62,9 @@
* Runtime changes to the app-id (OSC-176) now limits the app-id string
to 2048 characters ([#1897][1897]).
* `colors.flash-alpha` can no longer be set to 1.0 (i.e. fully
opaque). This fixes an issue where the window would be stuck in the
flash state.
[1897]: https://codeberg.org/dnkl/foot/issues/1897