Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!NORTHSTAR.DARTMOUTH.EDU!tobeye
From: tobeye@NORTHSTAR.DARTMOUTH.EDU (Anthony Edwards)
Newsgroups: comp.soft-sys.andrew
Subject: link inset usage disables keys
Message-ID: <UbIhU0i1eVXqEnH1ta@northstar.dartmouth.edu>
Date: 27 Nov 90 21:17:52 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 19

In a previous note I describe the scenario whereby I have a bunch of
link inset buttons; when I hit a button, a window appears with that
file.  The only problem is that there is no cursor in the new ez window.
 If I hit cursor keys, they are ignored.  I presume my keystrokes are
being directed to the link inset.  However, in the new window I don't
have a link inset button - just raw ascii text in  a textview inset.

All it takes is a mouse click in that window to activate the keystrokes.

I'd like to make the suggestion that when the link inset launches its
secondary window, it activates whatever inset is in that window (or at
the top).  Certainly I find it annoying in my context of editing, but I
think it's a misfeature for help, too.  Let's face it, most help files
are longer than a window size.  The most natural thing for me is to go
for the cursor keys (page down particularly) to see more text.  I can't
do that if the window is launched by a link inset button; not unless I
click in it first.

   - Anthony