Clients » History » Version 15
« Previous -
Version 15/16
(diff) -
Next » -
Current version
Christoph Kappel, 02/09/2018 11:40 AM
Clients¶
- Table of contents
- Clients
Clients are the actual toplevel windows subtle manages.
Types¶
There are several different window types that set some of the client modes automatically, this can be used in tagging to mimic this behavior.
Following types exist:
Normal¶
This is the default type of windows and no special modes are set for this.
Desktop¶
Desktop type windows are usually file managers that display icons and stay at the bottom of the window stack. They have no window title, no border and can neither be resized nor moved.
Used modes: Borderless, Fixed, Fullscreen
Dock¶
Dock type windows are usually panels that provide different kind of information and accessibility.
Toolbar¶
Toolbar windows are usually windows with either text or icons menu entries.
Splash¶
Splash windows are usually silly progress windows that are a placeholder until an app is ready.
Dialog¶
Dialog windows are usually any kind of setting or message windows
Properties¶
Clients have different properties, called atoms in Xorg, to e.g. identify the window or to communicate with other programs and the window manager. The typical way to list them is to use the program xprop, which used to be part of the Xorg install, but might be broken into a separate package dependent on your distribution. Just start xprop and click on a window, but be aware that the output is quite messy.
The instance and the class name are also included in the output of subtler -cl
.
WM_NAME¶
This property is used as the window title of the client.
Example:
$ xprop | grep WM_NAME
_NET_WM_NAME(UTF8_STRING) = "tmux:xprop3"
WM_NAME(STRING) = "tmux:xprop3"
WM_CLASS¶
This property consists of two strings: The instance name and the class name. They are mainly used to identify the window instance and to find resources in the resource files like .Xdefaults
. The instance name can typically be customized by passing something like -name name to the app like for most of the terminals.
Example:
$ xprop | grep WM_CLASS
WM_CLASS(STRING) = "urxvt", "URxvt"
WM_ROLE¶
This property is sometimes used to identify the purpose of the window, like a browser or something else in the context of the program, but don't expect useful or consistent values.
Example:
$ xprop | grep WM_ROLE
WM_ROLE(STRING) = "browser"
Modes¶
A window can have different modes that influence the appearance and behavior of it either globally or just for tagged views. subtle and subtler indicate this mode with a special character.
Following modes exist:
Global¶
Borderless¶
This mode disables the window border of the window and uses the additional space for the window.
Fixed¶
This mode prevents the window from being resized, that means that all actions (like fullscreen and gravity) that would change the size are ignored.
Resize¶
This mode enables the honoring of size hints, that are hints for the window manager about special size preferences and constraints like an aspect ratio.
Sticky¶
This mode overrides the tagging and makes the window visible on all views on the same screen. When a window isn't normally visible on a certain view the current gravity instead of the default gravity will be used.
Zaphod¶
This mode spans a window across all screens regardless if the window is normally visible there.
Per view¶
Floating¶
This mode looses the window from the gravity grid and raises it above other windows. Size hints are automatically honored in floating mode and windows can be moved and resized. (Doing that with gravitated windows enables floating mode)
Fullscreen¶
This mode let's a window use the total space of screen, that includes all space that is normally used for panels and strut.
Urgent¶
This mode automatically draws pointer and keyboard focus and highlights the panel title and any view. Once the window gets focus this mode is removed.
Stacking¶
There are four stacking layers, ordered from top to bottom: