You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was a side-effect of fixing another bug where some keys (notably the cursor keys) returned two values in quick succession - a 0 followed by its actual value.
On 11-12-2018 11:32, Michael McConnell wrote:
This was a side-effect of fixing another bug where some keys (notably
the cursor keys) returned two values in quick succession - a 0
followed by its actual value.
Ah, so fixing the bug in keyboard.c removes the need for it in the
caller.
Is there a reason for GET/GET$/INKEY/INKEY$ and elsewhere to use constructions like this?
do {
ch=emulate_get() & 0xFF;
} while (ch==0);
It means that Ctrl-@ is never passed back to the caller.
The text was updated successfully, but these errors were encountered: