A Perplexing Issue

[NakedApe]

My first guess is that you may have a _DISPLAY statement somewhere else in your code affecting screen output. Try placing an _AUTODISPLAY command where you have INPUT n. If this is the case then the INPUT statement is somehow over-riding this and may need to be looked into (a bug?).

Brilliant. I shoulda figured that out... Thanks, Terry! That was the issue. _AUTODISPLAY fixed it, so _DISPLAY may have an issue with INPUT.

Thanks again. 

Happy I could help

This same thing happens to me every time I write a new game. At some point I lose track of where _DISPLAY is controlling screen output and eventually expected screen updates don't happen. 99% of the time when output acts strange or doesn't happen when expected I always start with tracing my _DISPLAY and _AUTODISPLAY statements. _DEST can also be another reason for unexpected output, with the output going to a different image canvas than expected. If my _DISPLAY statements look fine then I starting tracing _DEST and _SOURCE.

I was thinking about INPUT and how it was affecting your output. After some thought I suppose it makes sense that INPUT would force a _DISPLAY otherwise the user would never see the input prompt. Perhaps not a bug but intended?

Re: INPUT forcing _DISPLAY, I'm glad it works that way - otherwise I would've gone totally crazy. In hindsight I'd say it's intentional bwdik!