From 9f2eb07ce648f514aff74cccaeed4867d13d493d Mon Sep 17 00:00:00 2001
From: nick black <dankamongmen@gmail.com>
Date: Sat, 25 Sep 2021 22:26:06 -0400
Subject: [PATCH] make pixel implementation choice clearer

We were using the value of pixel_shutdown to decide
whether we needed to take a kitty-specific path or
not. Instead, just use the pixel_implementation field
of tinfo, which was added a few weeks back.
---
 src/lib/sprite.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/lib/sprite.c b/src/lib/sprite.c
index 883df47e4..d923c2016 100644
--- a/src/lib/sprite.c
+++ b/src/lib/sprite.c
@@ -51,7 +51,7 @@ void sprixel_free(sprixel* s){
 sprixel* sprixel_recycle(ncplane* n){
   assert(n->sprite);
   const notcurses* nc = ncplane_notcurses_const(n);
-  if(nc->tcache.pixel_shutdown == kitty_shutdown){
+  if(nc->tcache.pixel_implementation >= NCPIXEL_KITTY_STATIC){
     sprixel* hides = n->sprite;
     int dimy = hides->dimy;
     int dimx = hides->dimx;