RE: Keyboard mapping - feedback

[Buck talking about changing PREVWORD to stop at empty input fields too]

>If you're going to do that, maybe you should
>make it something else (like K_PREVFIELD,
>K_NEXTFIELD) so that we can allow the two
>different functions to co-exist.

I will do just that, but I need to move in baby steps, so I'll tinker the
existing function for the moment.  My particular problem is knowing all the
places that I need to look at to implement a new keyboard function.  Once I
get that figured out, I'm going to try for 'newline'.

>Isn't that like a field exit thing?

No, Field Exit on 16.4 works great.  I'm talking about speeding the cursor
through an input-capable field.  Imagine a PDM screen where you want to
change a typo in the middle of the text column.  <tab><tab><hold down cursor
key for a while>.  I want to hold down the shift key and press right arrow 6
times and jump right to it.  And when I'm done, I want to do the same thing
to move the cursor back to the Option field on the next line.  Right now, it
jumps to the next non-blank field on the next line (the input inhibited
program name).

Very cool design.  I can't wait to be useful!
  --buck