From 984083bf19d15db5972bfda1e9d2e205f6015ddd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20Ekl=C3=B6f?= Date: Sun, 4 Oct 2020 19:22:47 +0200 Subject: [PATCH] =?UTF-8?q?sixel:=20cell-size-changed:=20don=E2=80=99t=20v?= =?UTF-8?q?erify=20sixels=20here?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The state after this function is an intermediate state and isn’t necessarily valid. This sixels needs to be ‘reflowed’ to ensure a valid state. This is something that should be done by the caller after the text grid has been reflowed and the sixel coordinates have been re-mapped to the new grid. TODO: can/should we update the sixel cols/rows in sixel_reflow() instead? --- sixel.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/sixel.c b/sixel.c index 2696f211..ee34df0a 100644 --- a/sixel.c +++ b/sixel.c @@ -518,7 +518,6 @@ sixel_cell_size_changed(struct terminal *term) six->rows = (six->height + term->cell_height - 1) / term->cell_height; six->cols = (six->width + term->cell_width - 1) / term->cell_width; } - verify_sixels(term); term->grid = &term->alt; tll_foreach(term->alt.sixel_images, it) { @@ -526,7 +525,6 @@ sixel_cell_size_changed(struct terminal *term) six->rows = (six->height + term->cell_height - 1) / term->cell_height; six->cols = (six->width + term->cell_width - 1) / term->cell_width; } - verify_sixels(term); term->grid = g; }