kicad-developers team mailing list archive

[John Beard <john.j.beard@xxxxxxxxx>]

Hi,

I do (try to) use most dialogs with the keyboard (limited sensation in
my fingers make mice and especially touchpads less useful to me).

Correct handling of focus, tab-traversal and so on is also important
for accessibility reasons, as well as being indicative of a coherent
UI in general. It's pretty annoying to be able to fill in almost all
of a dialog, but have controls fail to work at random.

Especially a dialog with multiple fields, you don't want to force
users to a "hover+key to invoke, type, move mouse, click, type, enter"
workflow, when you could have a "hover+key, type, tab, type, enter"
workflow - you forced a hand to the mouse AND back which should be
entirely avoidable.

Cheers,

John
On Tue, Oct 9, 2018 at 7:59 PM Eeli Kaikkonen <eeli.kaikkonen@xxxxxxxxx> wrote:
>
>
>
> ti 9. lokak. 2018 klo 17.05 Jeff Young (jeff@xxxxxxxxx) kirjoitti:
>>
>> I think you had the latest; the GAL branch should have been up-to-date as well.
>>
>> I’ve found a likely cause of the single-character-filter issue and pushed a “fix”.
>
>
> It works with the latest master (808a7d94833f1a). The remaining issues are focus and selection related. I think accepting the selected net from the list is more important because when the user uses filtering (s)he already uses the keyboard. Selecting and opening the combobox with keyboard is probably rare, I don't know if anyone wants to use KiCad's dialogs (other than text and numbers) with keyboard. After all ECAD must be used with a pointer device anyways.
>
> Eeli Kaikkonen
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp