aboutsummaryrefslogtreecommitdiff
path: root/wayland.c
diff options
context:
space:
mode:
authorDaniel Eklöf <daniel@ekloef.se>2026-01-04 06:57:25 +0000
committerDaniel Eklöf <daniel@ekloef.se>2026-01-04 17:59:20 +0000
commitb78cc92322dd2ae431dbbb70bc681b4d603d844d (patch)
treee7b412b09a1bad2a2917770a774015af641d9f90 /wayland.c
parentcsi: 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.c')
-rw-r--r--wayland.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/wayland.c b/wayland.c
index 6785c52d..958e535d 100644
--- a/wayland.c
+++ b/wayland.c
@@ -240,11 +240,8 @@ shm_format(void *data, struct wl_shm *wl_shm, uint32_t format)
struct wayland *wayl = data;
switch (format) {
- case WL_SHM_FORMAT_XRGB2101010: wayl->shm_have_xrgb2101010 = true; break;
case WL_SHM_FORMAT_ARGB2101010: wayl->shm_have_argb2101010 = true; break;
- case WL_SHM_FORMAT_XBGR2101010: wayl->shm_have_xbgr2101010 = true; break;
case WL_SHM_FORMAT_ABGR2101010: wayl->shm_have_abgr2101010 = true; break;
- case WL_SHM_FORMAT_XBGR16161616: wayl->shm_have_xbgr161616 = true; break;
case WL_SHM_FORMAT_ABGR16161616: wayl->shm_have_abgr161616 = true; break;
}