Re: [Cronometer-development] Recent interface changes

[<aa...@sp...>]

> Regarding the "Add Serving" button.  I am used to keyboard shortcuts
> in the Windows fashion (underlined letter indicates which letter to use
> with the alt key).

Control-Letter menu shortcuts have been standard practice around on
Windows since at least Windows 3.x.... I can look at adding alt-key
accelerators as well.

> I am not sure I understand the double-tabbing choice however.  If
> you were to use single tab to move from the match input field to the
> list then to the amount field, wouldn't it give exactly the same behaviour
> and allow the user to optionally stop off at the list and use the arrow
> keys to change the selection, while maintaining expected behaviour?

Not quite that simple because then clicking an item would no longer
transfer focus. I can try and detect the difference between a click and a
tab, and handle it differently...we'll see.

It takes two tabs to select the top item -- one tab to select the table
itself, then the second tab selects the row within it. A normal table then
has tab cycle through every cell, then when it reaches the very last cell,
it goes on to the next component. If your search results had a lot of
hits, it could take a lot of tabs to exit. It's tricky stuff to get right
in Java. I'll spend some more time playing with it.