ðòïåëôù 


  áòèé÷ 


Apache-Talk @lexa.ru 

Inet-Admins @info.east.ru 

Filmscanners @halftone.co.uk 

Security-alerts @yandex-team.ru 

nginx-ru @sysoev.ru 

  óôáôøé 


  ðåòóïîáìøîïå 


  ðòïçòáííù 



ðéûéôå
ðéóøíá












     áòèé÷ :: Filmscanners
Filmscanners mailing list archive (filmscanners@halftone.co.uk)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: filmscanners: Need feedback on VueScan Idea



Mike Kersenbrock wrote:

> EdHamrick@aol.com wrote:
>
> > Also, I was asked by one person to put the buttons at the top, above
> > the tabs.  This ends up looking quite cluttered, and it's easy to press
> > a tab instead of a button, and vice versa.  Putting the buttons at
> > the bottom and having the menus and tabs at the top seems to be
> > quite natural.  Unless someone can come up with a convincing
> > argument for putting the buttons at the top, I'm planning on leaving
> > them at the bottom.
>
> Main reason for it is the same reason that many "toolbars" in programs are
> at the top just below the menus.  The reason is mouse movement.  If one
> exclusively uses one set or the other as alternatives, then it doesn't
> matter -- but if one goes from one to the other during use, then mouse
> movement is minimized ("ease of use") by having them next to another.
>

But, a properly designed program usually uses speed keys for the buttons
anyway, and location is not a concern. I have yet to meet many users that
don't recohgnize the efficiencies picked up by shortcuts, aliases, and speed
keys. Even the function keys can be programmed to handle the tabs.

Jim Snyder, Software Engineer




 




Copyright © Lexa Software, 1996-2009.