Re: lynx-dev Re: Changing the keymap code (PATCH)

From:

Doug Kaufman

Subject:

Re: lynx-dev Re: Changing the keymap code (PATCH)

Date:

Sat, 6 Feb 1999 15:50:15 -0800 (PST)

On Sat, 6 Feb 1999, Kim DeVaughn wrote:
> Despite the above description, I'm not sure what the intent of
> your patch really is.
>
> I do know that it does NOT fix the problem with the disappearing
> statusline when a reset/select "button" is activated, which is
> what the patch I posted was addressing. (Which was caused by the
> addition of the MOUSE_KEY 0x10e define to LYStrings.h in -dev.8.)
This has nothing to do with fixing the statusline problem or
MOUSE_KEY. Klaus had written questioning what all the ifdef's were
doing in the keymap[] code. This is an effort to CLARIFY what was done
before. I never understood what the MOUSE_KEY code was doing. Mouse
isn't enabled on any system that I use, so I wasn't able to test any
of it.
Your patch to LYKeymap.c will break the default mappings for DOS and
Windows.
>--- ../../lynx-2.8.2-dev.15+kd.orig/src/LYKeymap.c Tue Feb 2 01:35:07 1999
>+++ LYKeymap.c Fri Feb 5 10:45:24 1999
>@@ -229,8 +229,8 @@
> LYK_HELP, LYK_ACTIVATE, LYK_HOME, LYK_END,
> /* F1*/ /* Do key */ /* Find key */ /* Select key */
>
>-LYK_UP_TWO, LYK_DOWN_TWO,
>-/* Insert key */ /* Remove key */
>+LYK_UP_TWO, LYK_DOWN_TWO, LYK_MOUSE_KEY,
>+/* Insert key */ /* Remove key */ /* rodent dummy */
I don't know what the best fix is, but inserting LYK_MOUSE_KEY here
will invalidate the mappings after it. Can't you put it at an unused
spot, such as 0x28f?
Doug
__
Doug Kaufman
Internet: address@hidden (preferred)
address@hidden