Linked by Thom Holwerda on Sun 25th Nov 2007 23:05 UTC
Graphics, User Interfaces This is the seventh article in a series on common usability and graphical user interface related terms [part I | part II | part III | part IV | part V | part VI]. On the internet, and especially in forum discussions like we all have here on OSNews, it is almost certain that in any given discussion, someone will most likely bring up usability and GUI related terms - things like spatial memory, widgets, consistency, Fitts' Law, and more. The aim of this series is to explain these terms, learn something about their origins, and finally rate their importance in the field of usability and (graphical) user interface design. In part VII, as promised in part VI, we focus completely on CDE, the Common Desktop Environment.
Thread beginning with comment 286861
To read all comments associated with this story, please click here.
Button State
by EricSchaefer on Mon 26th Nov 2007 10:08 UTC
EricSchaefer
Member since:
2007-11-26

In other words, the button does not only initiate/leave full-screen operation, it also indicates its state.


Well, buttons are supposed to trigger actions, not to show any state, besides being active or being inactive. The described behaviour is actually modal. To avoid modal buttons for maximizing and demaximizing would need two buttons. If the window is maximized, the maximize button would be deactivated. If the windows is not maximized, the unmaximize button would be deactivated. State should only be indicated by state labels, radio buttons and checkboxes, but never by pushbuttons.

Designers of everyday computer user interfaces could learn a lot from HMI designers (e.g. factory automation interfaces) and designers of non computer machine interfaces (old school HMI aka hardware pushbuttons).

Eric

Edited 2007-11-26 10:10

Reply Score: 1