Bill Gray

Just took the basic step of at least bringing `version.mif` from 3.4 to 4.0. At first, I agreed that we could rig up something to automatically update `version.mif` whenever `curses.h`...

Commit 1d32280adaa7d266c13 implements this (in a new `opaque_screen` branch so as not to break existing code), and also makes `SP` internal. Commit 2259f29d5f0be70fae077 addressed the one place where `SP` was...

An interesting point. At present, we need not break _anything_. Commit 0d5e4dc5b45b5108f48e "re-purposed" an existing void pointer in the `SCREEN` structure to point to an opaque structure (defined/used internally to...

Hmmm... you mean if they did something like ```c const SCREEN old_scr = *SP; (do various things, then decide you want to recover the old screen) *SP = old_scr; ```...

I think "close as not planned until we do something that breaks the ABI anyway." If we do that, I'd take the opportunity to make the `SCREEN`, and possibly `WINDOW`,...

I do see two possible problems here. First, the window is written out and read in as a stream of `chtype`s. If you created some files containing window data built...

One point I should check on, though : am I correct that this problem occurs when reading "old" files with "new" code? If you call `putwin()` and then `getwin()`, both...

@GitMensch , yes, this'll result in a new release. At least in theory, we could read "old-format" files and, with decent reliability, set the six new values reliably. For that...

@chuck-haatvedt , I'll have to get back to you on the Ctrl-C and Shift-End issues. I'm currently testing WinCon and WinGUI in Wine (no "real" Windows available to me right...

Hi Chuck, I tracked down a Win1 0 box, and found that Shift-End was detected in WinCon. This was tested using `testcurs`; go to the "Input Test" section and hit...