Changes from 3.4 to 3.5 on Windows? about pdcurses

[wmcbrine]

Using my psychic debugging powers...

Everything is, I suspect, working as designed. I think the problem is that you're exiting the program immediately, and expecting it to leave output on the screen. That works in the Windows console version of 3.4, but it isn't a behavior you should rely on -- some other ports of PDCurses never even write to a console. And in 3.5, the Windows console port, by default, switches to its own buffer while running, and switches back at the end, so it leaves nothing on screen. See here:

#4

You can try "set PDC_RESTORE_SCREEN=0", as described there; but the simplest thing would be to put a getch() before the endwin(), so that the program stays open until the user presses a key.

[matkuki]

Hey @wmcbrine ,
Your psychic powers are spot on! Both solutions work like a charm!
Thanks for the explanation.