Re: lynx-dev Keys, an attempt to understand

[Henry Nelson]

> from the djgpp.key file). Because the arrow keys and page[up/down]
> keys have special handling in the lynx code, these values couldn't
> be changed successfully (hence the need for the switch statement). I

I'm not able to follow this.  It doesn't matter if it's days or weeks
down the line (I know your busy), but could you try explaining again.

I think where I am misunderstanding (Klaus's explanation didn't quite
sink in) is why it is necessary for Lynx to translate from the code
received to some fixed value?  Isn't it possible to convert, outside
of Lynx, the key codes to codes that Lynx expects (are the "norm")?

If this is all a question of portibility, I wonder if the switch
statements could be handled in a separate module used for picking
up and interpreting key input.  Lynx proper, then, would have only
one mapping scheme, not two.

__Henry