diff options
| author | Daniel Eklöf <daniel@ekloef.se> | 2026-01-04 06:57:25 +0000 |
|---|---|---|
| committer | Daniel Eklöf <daniel@ekloef.se> | 2026-01-04 17:59:20 +0000 |
| commit | b78cc92322dd2ae431dbbb70bc681b4d603d844d (patch) | |
| tree | e7b412b09a1bad2a2917770a774015af641d9f90 /wayland.h | |
| parent | csi: secondary DA: fix comment; we don't use an XTerm version number (diff) | |
shm: don't bother with xrgb surfaces, always use argb
Before this patch, foot used xrgb surfaces for all fully opaque
surfaces, and only used argb surfaces for the main window when the
user enabled translucency.
However, several compositors have damage-like issues when we switch
between opaque and non-opaque surfaces (for example, when switching
color theme, or when toggling fullscreen).
Since the performance benefit of using non-alpha aware surfaces are
likely minor (if there's any measurable performance difference at
all!), lets workaround these compositor issues by always using argb
surfaces.
Diffstat (limited to 'wayland.h')
| -rw-r--r-- | wayland.h | 3 |
1 files changed, 0 insertions, 3 deletions
@@ -502,11 +502,8 @@ struct wayland { bool use_shm_release; bool shm_have_argb2101010:1; - bool shm_have_xrgb2101010:1; bool shm_have_abgr2101010:1; - bool shm_have_xbgr2101010:1; bool shm_have_abgr161616:1; - bool shm_have_xbgr161616:1; }; struct wayland *wayl_init( |
