mirror of
https://codeberg.org/dnkl/foot.git
synced 2026-02-05 04:06:08 -05:00
Revert "config: don't allow colors.flash-alpha to be 1.0"
This reverts commit 56d2c3e990.
This commit is contained in:
parent
c2add346ad
commit
301101e7d9
3 changed files with 2 additions and 26 deletions
21
render.c
21
render.c
|
|
@ -1898,27 +1898,6 @@ render_overlay(struct terminal *term)
|
|||
break;
|
||||
|
||||
case OVERLAY_FLASH:
|
||||
/*
|
||||
* 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
|
||||
* not allowing colors.flash-alpha to be 1.0.
|
||||
*/
|
||||
xassert(term->conf->colors.flash_alpha != 0xffff);
|
||||
|
||||
color = color_hex_to_pixman_with_alpha(
|
||||
term->conf->colors.flash,
|
||||
term->conf->colors.flash_alpha);
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue