diff options
| author | Alexander Orzechowski <alex@ozal.ski> | 2025-01-05 02:36:33 +0000 |
|---|---|---|
| committer | Daniel Eklöf <daniel@ekloef.se> | 2025-01-18 08:23:41 +0000 |
| commit | de3becef96f30b96f0fceddf73805c3951ccb59f (patch) | |
| tree | 66edfcf809618df064f6a30d1c18b4946fc5002b /render.c | |
| parent | terminal: Refresh only overlay when flash expires (diff) | |
Revert "config: don't allow colors.flash-alpha to be 1.0"
This reverts commit 56d2c3e990509d18de31e6009e0d0c6254f99b67.
Diffstat (limited to 'render.c')
| -rw-r--r-- | render.c | 21 |
1 files changed, 0 insertions, 21 deletions
@@ -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); |
