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

[Kim DeVaughn]

[IZ cc'd]

On Sun, Feb 07, 1999, Ilya Zakharevich (address@hidden) said:
|
| > Seriously ... it will take someone more familier with the DOS side
| > of things than I am (who is also UNIX literate), to implement the
| > proper fix.  I was hoping that the originator of the MOUSE_KEY stuff
| > (IZ, I think), would have had a chance to comment on the problem by
| > now ... perhaps in a few days, or so.
|
| I would do it earlier, but I have no idea what problem the patch is
| addressing, and how it is addressing it.  Looking up the thread does
| not help.

See the thread 'Nitsy "reset" display buglet', and the subthread
'[dev15] patch for mouse key buglet' for the background details
(all messages posted on 02/05/99).

Basically, there was a define for MOUSE_KEY added in LYStrings.h
for the -dev.8 release, which resulted in the observable behavior
of the statusline getting blanked out when a reset button or select
was activated.  [I dunno if there are other, non-visible side-effects,
but that is what one can easily *see* on all releases since then, at
least on UNIX/gcc builds (with either slang 1.2.2, or ncurses 4.2+).]

Since the only CHANGES for that release with the word "mouse" in them
are:

 1998-12-03 (2.8.2dev.8)
 [...]
 * improvements to mouse code, ncurses-based, from IZ (Ilya Zakharevich)
   a) Mouse navigation inside text entry fields;
   b) Mouse navigation to a text entry field (including an empty one)
   c) Mouse navigation to a specific position of a text field (since I do not
      know which fields are text fields, I implemented "b" and "c" for
      F_TEXTAREA_TYPE and F_TEXT_TYPE only, search for these symbols in the
      patch);
   d) Mouse navigation in menus:  To scroll, one can click on top/bottom border
      (single=byline, double=bypage, triple=beg/end), or above/below menu
      (single=bypage, double=beg/end)) mouse-3 ==> quit;
   e) Double-click-1 on the first and last row are interpreted as goto-
      start/end/main-window (depending on the location of the click).
   Other Changes:
   a) Ask ncurses for all mouse events, but increase mouseinterval() to simulate
      current behavior (which is effectively an infinite mouseinterval() +
      masking of repeated clicks);
   b) Earlier clicking to the left of a link would activate the link.  I see no
      use for this, so consider this a bug.

I presume that that was the source of the MOUSE_KEY define, etc, which
ended up causing the statusline problem.  I apologize if that is not the
case.

Anyway, hope you can take a look at it now ...

/kim


| P.S.  Note that I do not subscribe, and it is a PITA to reply via the
|       mail archive list.

Ain't it the truth ... but better than nothing.