Virgil Dupras 475caf35f4 Make KEY non-blocking ... ... and rename it to KEY?. Then, add KEY from KEY? for its blocking version. I need this for an upcoming Remote Shell feature. If a Collapse OS system remotely controls another shell, it needs to be able to poll both the remote system and the local keyboard at the same time. A blocking KEY is incompatible with this. In some places, the polling mechanism doesn't make sense, so this new KEY? always returns a character. In some places, I just haven't implemented the mechanism yet, so I kept the old blocking code and added a "always 1" flag as a temporary shim. I have probably broken something, but in emulators, Collapse OS runs fine. It's an important reminder of what will be lost with the new "dogfooding" approach (see recent mailing list message): without emulators, it's much harder to to sweeping changes like this without breaking stuff. It's fine, I don't expect many more of these core changes to the system. It's nearly feature-complete.		2021-01-01 08:23:59 -05:00
..
rc2014	Make KEY non-blocking	2021-01-01 08:23:59 -05:00
sms	Make KEY non-blocking	2021-01-01 08:23:59 -05:00
ti84	Make KEY non-blocking	2021-01-01 08:23:59 -05:00
trs80	Make KEY non-blocking	2021-01-01 08:23:59 -05:00
z80mbc2	Make KEY non-blocking	2021-01-01 08:23:59 -05:00