Context-sensitive user interface

A context-sensitive user interface is one which can automatically choose from a multiplicity of options based on the current or previous state(s) of the program operation.[1] Context sensitivity is almost ubiquitous in current graphical user interfaces, usually in the form of context menus. Context sensitivity, when operating correctly, should be practically transparent to the user. This can be experienced in computer operating systems which call a compatible program to run files based upon their filename extension, e.g. opening text files with a word processor, video files (.mpg, .mov and .avi, etc.) with a video player, image files (.jpg and .png etc.) with a photo viewer or running program files themselves, and their shortcuts, (i.e. .exe files) when selected.

The user-interface may also provide Context sensitive feedback, such as changing the appearance of the mouse pointer or cursor, changing the menu color, or with applicable auditory or tactile feedback.

Reasoning and advantages of context sensitivity

The primary reason for introducing context sensitivity is to simplify the user interface.

Advantages include:

  • Reduced number of commands required to be known to the user for a given level of productivity.
  • Reduced number of clicks or keystrokes required to carry out a given operation.
  • Allows consistent behaviour to be pre-programmed or altered by the user.
  • Reduces the number of options needed on screen at one time.

Disadvantages

Context sensitive actions may be perceived as dumbing down of the user interface - leaving the operator at a loss as to what to do when the computer decides to perform an unwanted action. Additionally non-automatic procedures may be hidden or obscured by the context sensitive interface causing an increase in user workload for operations the designers did not foresee.

A poor implementation can be more annoying than helpful – a classic example of this is Office Assistant.

Implementation

At the simplest level each possible action is reduced to a single most likely action – the action performed is based on a single variable (such as file extension). In more complicated implementations multiple factors can be assessed such as the user's previous actions, the size of the file, the programs in current use, metadata[2] etc.

The method is not only limited to the response to imperative button presses and mouse clicks - pop-up menus can be pruned and/or altered, or a web search can focus results based on previous searches.

At higher levels of implementation context sensitive actions require either larger amounts of meta-data, extensive case analysis based programming, or other artificial intelligence algorithms.

In computer and video games

Context sensitivity is important in video games – especially those controlled by a gamepad, joystick or computer mouse in which the number of buttons available is limited. It is primarily applied when the player is in a certain place and is used to interact with a person or object. For example, if the player is standing next to a non-player character, an option may come up allowing the player to talk with him/her.

Implementations range from the embryonic 'Quick Time Event' to context sensitive sword combat in which the attack used depends on the position and orientation of both the player and opponent, as well as the virtual surroundings. A similar range of use is found in the 'action button' which, depending upon the in-game position of the player's character, may cause it to pick something up, open a door, grab a rope, punch a monster or opponent, or smash an object.[3]

The response does not have to be player activated - an on-screen device may only be shown in certain circumstances, e.g. 'targeting' cross hairs in a flight combat game may indicate the player should fire. An alternative implementation is to monitor the input from the player (e.g. level of button pressing activity) and use that to control the pace of the game in an attempt to maximize enjoyment or to control the excitement or ambience.[4]

The method has become increasingly important as more complex games are designed for machines with few buttons (keyboard-less consoles). Bennet Ring commented (in 2006) that "Context-sensitive is the new lens flare".[5]

Context-sensitive help
Main article: Context-sensitive help

Context sensitive help is a common implementation of context sensitivity, a single help button is actioned and the help page or menu will open a specific page or related topic.[6]

gollark: I want neutron SOLID instead because WHY NOT.
gollark: I like MSRs but I just skipped to fusion because fusion is cool.
gollark: It's probably more *efficient* to custom-design multiple layers, but it's harder.
gollark: If you do D-D you then get loads of nice byproducts (neutron fluid included) you can feed into MORE reactors.
gollark: NEVER!

See also

References

Citations
  1. Webopedia : context sensitive
  2. Alan Dix; Tiziana Catarci; Benjamin Habegger; Yannis Ioannidis; Azrina Kamaruddin; Akrivi Katifori; Giorgos Lepouras; Antonella Poggi; Devina Ramduny-Ellis. "intelligent context-sensitive interactions on desktop and the web" (PDF). Archived from the original (PDF) on 2007-03-06. Retrieved 2008-07-29. Cite journal requires |journal= (help)
  3. "Assassin's Creed E3 Preview". Archived from the original on 2007-08-03. Retrieved 2008-07-29.
  4. Next Generation User Interfaces (A MIT Computer Science Masters Thesis by Eitan Glinert)
  5. Gears of War review - Now this is what next-gen gaming is all about
  6. Webopedia : Help

Sources
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.