Finally getting hold of the English Sedoric 3 manual (thanks again Steve!) I noticed the KEY OFF and KEY SET commands.
One of the minor things that still nagged me about my program is that if you push a button to often it remembers that button, making the next popup waiting for a key immediately to disappear again.
In my original code on the C128 I had a POKE code for this in the code to clear the keyboard buffer, but did not find an equivalent yet on the Oric.
So the KEY OFF and KEY SET commands seemed a solution, as it bascially shuts off the keyboard, so also no keypress to be remembered. And according to the manual, the code even runs 20% faster with KEY OFF, so great.
Indeed doing this prevents keys to be remembered and pop-ups to disappear directly again.
However, with a big downside, it was completely screwing up the music played. Which sort of makes sense, as KEY OFF / KEY SET interfere with the interrupts, while also the music routine runs via interrupts.
So is it indeed normal behaviour that setting KEY OFF and KEY SET again and again does not play nice with the music playing routines? Anyone tried this? And maybe came with a workaround?
For now removed the KEY OFF and KEY SET commands again as I did not want to sacrifice music for it.
Looking for alternatives, I saw this article on the OSDK site: https://osdk.org/index.php?page=articles&ref=ART16
Nothing on a keyboard buffer there and clearing it, but I did see that the last keypress is apparently at address 735 ("$2DF (735) Contains the ASCII code + 128 of the last pressed key"). So thought, lets try POKEing a zero to 735 and see if that helps.
And yes, it does seem to work. Is this indeed the way to clear a keyboard buffer and remove any last pressed key?
See that the article I refer to is intriguingly called Keyboard handling (1), so will there be a part (2) that maybe also covers this?