> I have another idea. We could have the userInterruptWatcher poll
> (use a timeout on waiting for the interrupt semaphore), and if
> it's been "too long" since the last time that events were
> checked for, then do a peekKeyboard or equivalent (get more
> events and flush all the non-keyboard ones).
>
> Then respond to the interrupt key (if any) the usual way.
>
> I'll try this.

Y'know that'll work for sure. It used to be called ioProcess not too many
CSes ago ;-)

Cheers,
  - Andreas