User Interface Improvements: Buttons
PostPosted: Thu Nov 03, 2005 11:32 pm
Hard to see when new to Silverfast:
Although already very small, some of the buttons are subdivided into "subbuttons", launching different functions depending on the edge they are touched. This does not comply with windows standard (Mac probably too) and even when someone has registered this, it is difficult to handle. I suggest to provide one function per button. In order to maintain overview, the buttons should be grouped by function (with some space between groups). In some cases, functions may be combined such as black point and white point: these data may be displayed simutaneously.
<img src="/img/forum/isrd.gif" align="right" hspace="5" vspace="5">Another bad idea is using the buttons as a display for the function status:
It is very difficult to see if a function like iSRD is on or off: The symbols look nearly the same - different colors are almost not recognisable at this size. If you want to continue using buttons for a status display, use well distinguishable symbols like that: function on: symbol as known, function off: symbol with a big cross overlay. The tooltips should be adjusted accordingly (do now have always the same text regardless of the status).
A good windows program has a menu with all commands. Buttons for these functions are an extra for simplifiing access to frequently used functions. This reduces the button count to an overlookable number.
A menu is also a good place to indicate keyboard shortcuts for more frequently used functions (would you search the documentation for this information ?). A compromise would be to show the shortcuts in the tooltip text for the buttons.
Eckart M?rkel
Although already very small, some of the buttons are subdivided into "subbuttons", launching different functions depending on the edge they are touched. This does not comply with windows standard (Mac probably too) and even when someone has registered this, it is difficult to handle. I suggest to provide one function per button. In order to maintain overview, the buttons should be grouped by function (with some space between groups). In some cases, functions may be combined such as black point and white point: these data may be displayed simutaneously.
<img src="/img/forum/isrd.gif" align="right" hspace="5" vspace="5">Another bad idea is using the buttons as a display for the function status:
It is very difficult to see if a function like iSRD is on or off: The symbols look nearly the same - different colors are almost not recognisable at this size. If you want to continue using buttons for a status display, use well distinguishable symbols like that: function on: symbol as known, function off: symbol with a big cross overlay. The tooltips should be adjusted accordingly (do now have always the same text regardless of the status).
A good windows program has a menu with all commands. Buttons for these functions are an extra for simplifiing access to frequently used functions. This reduces the button count to an overlookable number.
A menu is also a good place to indicate keyboard shortcuts for more frequently used functions (would you search the documentation for this information ?). A compromise would be to show the shortcuts in the tooltip text for the buttons.
Eckart M?rkel