[Coco] PEEK for detecting CoCo arrow keys, etc.?

[Arthur Flexser]

If you are running something in assembly, Basic will not be scanning the
keyboard, through interrupts or anything else.  Basic does not use
interrupts for keyboard scanning.

The rollover table's main purpose, I believe, is to prevent keyboard bounce.

Art

On Sat, Dec 20, 2014 at 6:06 PM, Allen Huffman <alsplace at pobox.com> wrote:

> Thank you, Art and Rogelio, for this. I remember “keyboard rollover table”
> now, but not the details. If the keyboard was read through two PIAs (8 bits
> each), why did they split that out in to 8 memory locations in BASIC?
>
> If I was writing something in assembly, I assume all of this is still
> polled by BASIC unless interrupts are disabled? (Scanning during the IRQ?).
>
> > On Dec 19, 2014, at 7:20 PM, Arthur Flexser <flexser at fiu.edu> wrote:
> >
> > Further...
> >
> > To determine which peek values correspond to which arrow keys, run the
> > following:
> >
> > 10 FOR I=&H152 TO &H159
> > 20 PRINT PEEK(I);:NEXT:GOTO 10
> >
> > Then press each arrow key to see which byte changes, and what value it
> > changes to, for that key.
> >
> > Art
>
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>