Dbug wrote: ↑
Sun Sep 23, 2018 12:47 pm
At one moment, when DBug wrote here (see his post) and told me that keyboard tempo was a bad thing, I changed the code in order to use peek(#208) instead of the key$ facility : bad idea. You were pressing a key, and you were falling from the building at the other side of the screen in fraction of a second.
I did not mean to use peek instead of what you were using.
The delay between repeat, and the delay before repeat, are two values in page two that can be used to control keyboard handling.
In a game you want a faster repeat value, and the initial delay should be identical to the other one.
Check in your manual for values 24E and 24F
It's been a long time since I code on an Oric, and at first I did not remember those two locations, that's why I introduced the peek thing.
When I saw it was not a good Idea, I documented myself, reading manuals carefully about keyboard handling.
But this is exactly what I am using in my code (in the how_high() procedure).
The default repetition values are set back for the input of the player name in the score update.
Anyway, thank you DBug, the game is really more playable with your advised piece of advice.
Here is the current code (lines 1204 and 1205) :
Code: Select all