In a computing graphical user interface (GUI), a component has focus when it is selected to receive input from the user by an event such as a mouse button click or keypress.[1] Moving the focus away from a specific user interface element is known as a blur event in relation to this element.[2] Typically, the focus is withdrawn from an element by giving another element the focus. This means that focus and blur events are virtually simultaneous in relation to different user interface elements, one that becomes focused and one that is "blurred" (in the computing, not visual, sense).
The concept is similar to a cursor in a text-based environment. However, when considering a graphical interface, there is also a mouse pointer involved. Moving the mouse will typically move the mouse pointer without changing the focus. The focus can usually be changed by clicking on a component that can receive focus with the mouse. Many desktops also allow the focus to be changed with the keyboard. By convention, the Tab ↹ key is used to move the focus to the next focusable component and ⇧ Shift Tab ↹ to the previous one. When graphical interfaces were first introduced, many computers did not have mice, so this alternative was necessary. This feature makes it easier for people unable to use a mouse to use the user interface. In certain circumstances the arrow keys can be used to change focus.
Window focus
editThe behaviour of focus on one's desktop can be governed by policies in window management.
Click to focus
editOn most mainstream user-interfaces, such as ones made by Microsoft and Apple, it is common to find a "focus follows click" policy (or "click to focus"), where one must click the mouse inside of the window for that window to gain focus. This also typically results in the window being raised above all other windows on screen. If a clickfocus model such as this is being used, the current application window continues to retain focus and collect input, even if the mouse pointer is over another application window.
Focus follows pointer
editAnother common policy on Unix systems using X Window System (X11) is the "focus follows mouse" policy (or FFM), where the focus automatically follows the current placement of the pointer. The focused window is not necessarily raised; parts of it may remain below other windows. Window managers with this policy usually offer "autoraise," which raises the window when it is focused, typically after a configurable short delay. A possible consequence of a followfocus policy is that no window has focus when the pointer is moved over the background with no window underneath; otherwise the focus simply remains in the last window.
Sloppy focus
editThe sloppyfocus model is a variant of the followfocus model.[3] It allows input to continue to be collected by the last focused window when the mouse pointer is moved away from any window, such as over a menubar or desktop area.
Focus models used by X11 window managers
edit| Clickfocus | Followfocus | Sloppyfocus | |
|---|---|---|---|
| aewm[4] | No | Yes | No |
| aewm [5] | Yes | No | No |
| AHWM[6] | Yes | No | Yes |
| awesome | Yes | Yes | Yes |
| CTWM | Yes | Yes | Yes |
| dwm[7] | Yes | Yes | No |
| E16 | Yes | Yes | Yes (default) |
| evilwm[8] | No | Yes | No |
| FLWM | No | No | Yes |
| Fluxbox | Yes | Yes | Yes |
| FVWM[α] | Yes | Yes (default) | Yes |
| IceWM[9] | Yes | Yes | Yes |
| Karmen[10] | Yes | No | No |
| lwm[11] | Yes | No | Yes |
| TinyWM[12] | No | No | Yes |
| Whim[13] | Yes | No | Yes |
| WindowLab | Yes (with no autoraise) | No | No |
| Xfwm | Yes | Yes | Yes |
| Mutter | Yes | Yes | Yes |
| JWM | Yes | No | Yes |
| MWM | Yes | No | No |
Intra-window component focus
editIndividual components of a window may also have a focal position. For instance in a text editing package, the text editing window must have the Focus so that text can be entered. When text is entered into the component, it will appear at the position of the text-cursor, which will also normally be movable using the mouse pointer.
Which component should have the default focus, and how focus should move between components, are difficult but important problems in user interface design. Giving the wrong thing focus means that the user has to waste time moving the focus. Conversely, giving the right thing focus can significantly enhance the user experience.
See also
editReferences
edit- ^ "Managing UI Component Focus - Concept of Focus". Enlightenment. Retrieved 4 June 2023.
- ^ Garg, Naman (12 October 2018). "Javascript Window Blur() and Window Focus() Method". GeeksforGeeks. Retrieved 4 June 2023.
- ^ "Sloppy Focus". c2.com/cgi/wiki. 25 February 2012.
- ^ "aewm - Red Bean". 27 December 2007. Archived from the original on 14 January 2016. Retrieved 16 January 2016.
- ^ "Guide to X11/Window Managers/aewm ". Wikibooks. 18 July 2010. Retrieved 16 January 2016.
- ^ "AHWM - Alex Hioreanu's Window Manager". hioreanu.net. 24 February 2014. Retrieved 16 January 2016.
- ^ "dwm - dynamic window manager". suckless.org. 9 November 2015. Retrieved 16 January 2016.
- ^ "evilwm - a minimalist window manager for the X Window System". The Dragon 32/64 Computers. 13 July 2015. Retrieved 16 January 2016.
- ^ "icewm(1)". 13 February 2021. Retrieved 16 February 2021.
- ^ "Karmen: A Window Manager for X". 28 December 2008. Retrieved 16 January 2016.
- ^ "lwm - Lightweight Window Manager". 26 February 2015. Retrieved 16 January 2016.
- ^ "incise.org: tinywm". 23 April 2014. Retrieved 16 January 2016.
- ^ "Whim basic information". Tcler's Wiki. 24 November 2009. Retrieved 16 January 2016.
Notes
edit- α Per window or window class, with additional support for "never focus" — windows that should never receive focus.