list_dialog()

[Tony Balinski]

Quoting "A.V.Kuznetsov" <kuzn at umps.mephi.ru>:

> On Fri, 29 Sep 2006 09:04:24 -0400
> Tony Balinski <ajbj at free.fr> wrote:
>
> Hi,
>
> > All debate aside, I have a working implementation of the keyword thing
> > (my vote option 4) - the patch is here:
> >   http://ajbj.free.fr/nedit/nedit5.5dev/patches/listDialogKeyWords.diff
> >
> > You'll find a description of changes (and the keywords implemented) at
> > the start of that file.
> >
> > Thorsten's "pass options as an array" idea appeals to me: I may have a
> > hack at that too.
> >
> > Give it a go: feedback would be nice...
>
> I tried to work with new dialog and found an incorrect(?) behavior.
> If string_entry is used, a string input line is active, i.e.
> cursor is placed in the line and keyboard's events lead to input of a
> string.
> In old list_dialog() a list is active and  keyboard's events lead to
> selection of an entry. Some users, like me, use keyboard for navigation
> in list. I think, a list should be active when dialog-window is opened.

I noticed this too. The string entry widget was always built into the
dialog we use. I just make sure it's activated. I have not paid any
attention to which widget gets the initial focus. As a workaround,
hitting [shift+]tab doesn't seem too much to ask of a user. But you
are right: focus on the list seems much better.

Tony