Re: [Cronometer-development] Recent interface changes

[Richard T. <ric...@gm...>]

On 1/22/07, aa...@sp... <aa...@sp...> wrote:
> For a more detailed analysis of why the change to the main window was
> made, and why it's faster, check out my recent post: http://spaz.ca/?p=219

Removing the search panel to a window is fine by me.  But I would like to
try and persuade you that the way it is now, it is not very simple to use
and does not behave in expected ways (although perhaps my
expectations are biased in some unreasonable manner by using
Windows).

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).   Understandably this is a Java application and I can't
expect Windows conventions to apply, but the next usability standard
(which comes to my mind at least) does not work either. That is being
able to give focus to a button and for the button to retain focus.  When
I use an application, I usually expect to be able to tab to a button, then
hit enter to select it.  And if it opens a window, then when the window
closes, focus remains on the button in the main window (and enter
can be hit again to get a new serving window).  But ctrl-e while
unexpected works fine of course.

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?

Anyway, thanks for your continuing work! :-)

Cheers,
Richard.