aboutsummaryrefslogtreecommitdiff
path: root/sixel.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 /sixel.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 'sixel.c')
-rw-r--r--sixel.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/sixel.c b/sixel.c
index 07b97f46..294864fd 100644
--- a/sixel.c
+++ b/sixel.c
@@ -125,12 +125,12 @@ sixel_init(struct terminal *term, int p1, int p2, int p3)
* that assumes 32-bit pixels).
*/
if (shm_chain_bit_depth(term->render.chains.grid) >= SHM_BITS_10) {
- if (term->wl->shm_have_argb2101010 && term->wl->shm_have_xrgb2101010) {
+ if (term->wl->shm_have_argb2101010) {
term->sixel.use_10bit = true;
term->sixel.pixman_fmt = PIXMAN_a2r10g10b10;
}
- else if (term->wl->shm_have_abgr2101010 && term->wl->shm_have_xbgr2101010) {
+ else if (term->wl->shm_have_abgr2101010) {
term->sixel.use_10bit = true;
term->sixel.pixman_fmt = PIXMAN_a2b10g10r10;
}