Mode (user interface): Difference between revisions

Content deleted Content added
Added wikilink to "diacritics"
Ylado (talk | contribs)
general copyediting
Line 1:
{{About|a transient state in user interfaces|modes in videogames|Game mode|other uses|Mode (disambiguation)}}
{{Distinguish|Multimodal interaction|Modality (human-computer interaction)}}
In [[user interface]] design, a '''mode''' is a distinct setting within a [[computer program]] or any physical machine [[Interface (computing)|interface]], in which the same [[user input]] will produce perceived results different from those that it would in other settings. The best-known '''modal'''Modal interface components are probablyinclude the [[Caps lock]] and [[Insert key|Insert]] keys on the standard [[computer keyboard]], both of which (typically) put the user's typing into a different mode after being pressed, then return it to the regular mode after being re-pressed.
 
An interface that uses no modes is known as a '''modeless''' interface.<ref>[http://www.usabilityfirst.com/glossary/term_321.txl Usability Glossary: modeless] {{webarchive|url=https://web.archive.org/web/20071022205105/http://www.usabilityfirst.com/glossary/term_321.txl |date=2007-10-22 }}</ref> Modeless interfaces avoid '''mode errors''', in which the user performs an action appropriate to one mode while in another mode, by making it impossible for the user to commit them.<ref>[http://www.usabilityfirst.com/glossary/mode-error/ Usability Glossary: mode error]</ref> by making it impossible for the user to commit them.
 
== Definition ==
A precise definition is given by [[Jef Raskin]] inIn his book ''[[The Humane Interface]]'', [[Jef Raskin]] defines modality as follows:
<blockquote>
"An human-machine interface is modal with respect to a given gesture
when (1) the current [[State (computer science)|state]] of the interface is not the user's [[Wiktionary:locus|locus]]<!-- (sic). Do not change this to "focus"; "locus" is the word used by the source, it means "place". --> of
attention and (2) the interface will execute one among several
different responses to the gesture, depending on the system's current
Line 20:
===Modal===
{{Expand section|the detailed description of typical uses of modes|date=December 2010}}
Several examples of well-known software have been described as ''modal'' and/or using interface modes:
* [[Text editor]]s – typically are in insert mode by default but can be toggled in and out of [[overtype]] mode by pressing the [[Insert key|Insert]] key.
* [[vi]] – has one mode for inserting text, and a separate mode for entering commands. There is also an "[[Ex (editor)|ex]]" mode for issuing more complex commands (e.g. search and replace). Under normal circumstances, the editor automatically returns to the previous mode after a command has been issued; however, it is possible to permanently move into this mode using ''Shift-Q''.
Line 35:
{{See also|User error}}
 
Modes are often frowned upon in interface design because they are likely to produce '''mode errors''' when the user forgets what state the interface is in, performs an action that is appropriate to a different mode, and gets an unexpected and undesired response.<ref>[http://www.usabilityfirst.com/glossary/mode-error/ Glossary: mode error]</ref><ref name="glossary">[http://www.usabilityfirst.com/glossary/modal Usability Glossary: modal]</ref> A mode error can be quite startling and disorienting as the user copes with the sudden violation of his or her [[user expectations]].
 
Problems occur if a change in the system state happens unnoticed (initiated by the system, or by another person, such as the user who was previously using the machine), or if after some time the user forgets about the state change. Another typical problem is a sudden change of state that interrupts a user's activity, such as [[focus stealing]]. In such a situation it can easily happen that the user does some operations with the old state in mind, while the brain has not yet fully processed the signals indicating the state change.