08-03-2022, 05:13 AM
Aye. A 32000 length page at 20 pixels per line gives us 1600 lines of text to scroll down, if we just hold the arrow and let it go -- and out of those, we're only printing on about 20 of them. When I start my actual text adventure, I'm going to add in a simple variable to the DisplayPage routine which counts total lines used on it, and then it can set that as the page bottom. At that point you won't be able to scroll past the text and those lost presses won't affect you anymore. That should eliminate most of the issue which you're talking about.
PageUp/PageDown to navigate a whole page of text at once would also be nice. (CTRL + PageUp/PageDown to jump to top/bottom as well.)
And if you look, I don't actually need a _KEYCLEAR. I use my custom keyboard library normally, so it takes care of that.
PageUp/PageDown to navigate a whole page of text at once would also be nice. (CTRL + PageUp/PageDown to jump to top/bottom as well.)
And if you look, I don't actually need a _KEYCLEAR. I use my custom keyboard library normally, so it takes care of that.