Re: TypeMatic Rate

Alan R.,

Yes, chain the interrupt, save status of keys you are watching, and
acknowledge the INT yourself. Other keys are passed through normally
(chain).

As the "arrow keys" (and + - keys) are often used elsewhere in a program
(menus, MDI, etc), the kbd vector should be chained when need for "kbd
jog", and restored when that mode is exited.

Just a thought, but I wonder if one could connect the A and B phases of
an encoder to keyboard keys? The keyboard's "key down, key up"
sequences could drive a software state machine in the "chained" ISR
code, and inc/dec a position counter. Yeah, that might work!

Alan KM6VV


beer@... wrote:

>
> > Why not chain the kbd interrupt, and "grab" the cursor keys used for JOG
> > before they are put into the kbd buffer? Watch for key down an key up
> > codes from the kbd controller. Then, typematic repeats don't seem to
> > matter... (what happens to them?)
>
> For those keys you want to process, simply swallow them up and don't
> pass them to the original keyboard ISR.
>
> Alan