On Fri, Jul 17, 2026 at 12:12:18PM -0400, Mouse wrote: > > It obviously is not the *right* fix, but it's good enough for me for > the moment. >
I am reasonably sure that the screen data structures get initialised later, some of it may occur on the first call to refresh(), other bits just after the screen is created. If you can absolutely show that we are referencing uninitialised data then sbutmit a PR and I will be happy to have a look. As a thought, I wonder if you are making things complicated for yourself, you could split your program into two cooperating processes, one that handles the async interactions with the hardware and the other handles the UI. That way you don't have to force the curses library into a no-wait situation when it is not expecting it - curses does handle not waiting in some situations but it is under the control of the library. -- Brett Lymn -- Sent from my NetBSD device. "We are were wolves", "You mean werewolves?", "No we were wolves, now we are something else entirely", "Oh"
