focus handling

focus handling

[Tom Tromey]

I noticed that the default focus for the source window doesn't seem to
be the text pane (ok, I'm assuming this is the case based on the
symptoms).  This means that when I use the up/down arrows or the page
up/down keys, the text doesn't scroll.  It does scroll once I use the
mouse to select some text (and thus presumably set the focus as a side
effect).

I think the arrow and page keys should work whenever the focus is
anywhere on the source window.

Tom

Re: focus handling

[James Ingham]

Tom,

The page keys should probably work wherever the focus is, but the
arrow keys have to work "whenever the focus is in the source window,
but NOT in the little search pane, or the file or function combo
boxes..."  Otherwise you couldn't correct text in the file box, for
example, before hitting a return to go to the file.  Either that or we 
need to make these combo boxes mouse-only (i.e. drop-down menus.)

There are other bindings like this that are wrong too.  "n" and "s"
are bound to next and step, but again only when you are focused on the 
source pane.  They too need to be "whenever you are NOT in the combo
or entry boxes".  This latter is a known bug.  All these bindings need 
tuning.

Jim

 > I noticed that the default focus for the source window doesn't seem to
 > be the text pane (ok, I'm assuming this is the case based on the
 > symptoms).  This means that when I use the up/down arrows or the page
 > up/down keys, the text doesn't scroll.  It does scroll once I use the
 > mouse to select some text (and thus presumably set the focus as a side
 > effect).
 > 
 > I think the arrow and page keys should work whenever the focus is
 > anywhere on the source window.
 > 
 > Tom
 >