The table below shows the supported combinations of window provider and GL backend on the 4 platforms:. For example, to force the display to be HDMI, use:. Check Controlling the environment to see all the possible values. If you are using the official Raspberry Pi touch display, you need to configure Kivy to use it as an input source.
Optionally, spectrwm can call baraction. The modkey the main key to issue commands with is set to Mod4 , which is usually the Super key. There is also a screen lock key binding, which by default calls xlock from the xlockmore package. See Xdefaults for details of how to set up fonts, colours and other settings for xterm and xscreensaver.
Run xscreensaver-demo to select the animation or blank and display power management recommended. In order to customize keybindings:. With a non-Xrandr multiple monitor setup create regions to split the total desktop area into one region per monitor:. By default they are commented out and the statusbar is disabled. To test the status bar, place the following simple baraction. Here are some other ideas for status bar items: ethernet, email notification, disk space, mounts, now playing mpc current.
Multiple MetaModes list the combinations of modes and the sequence in which they should be used. Here is an example MetaMode:. If you want a display device to not be active for a certain MetaMode, you can use the mode name "NULL", or simply omit the mode name entirely:. Optionally, mode names can be followed by offset information to control the positioning of the display devices within the virtual screen space; e. Offset descriptions follow the conventions used in the X "-geometry" command line option; i.
When no offsets are given for a MetaMode, the offsets will be computed following the value of the MetaModeOrientation option see below. When not explicitly given, the virtual screen size will be computed as the the bounding box of all MetaMode bounding boxes. MetaModes with a bounding box larger than an explicitly given virtual screen size will be discarded.
A panning domain is the area in which a display device's viewport will be panned to follow the mouse. Panning actually happens on two levels with MetaModes: first, an individual display device's viewport will be panned within its panning domain, as long as the viewport is contained by the bounding box of the MetaMode. Once the mouse leaves the bounding box of the MetaMode, the entire MetaMode i. Note that individual display devices' panning domains default to being clamped to the position of the display devices' viewports, thus the default behavior is just that viewports remain "locked" together and only perform the second type of panning.
The most beneficial use of panning domains is probably to eliminate dead areas -- regions of the virtual screen that are inaccessible due to display devices with different resolutions.
Specifying a panning domain for the second display device:. Offsets can be used in conjunction with panning domains to position the panning domains in the virtual screen space note that the offset describes the panning domain, and only affects the viewport in that the viewport must be contained within the panning domain. For example, the following describes two modes, each with a panning domain width of pixels, and the second display is positioned below the first:. Because it is often unclear which mode within a MetaMode will be used on each display device, mode descriptions within a MetaMode can be prepended with a display device name.
If no MetaMode string is specified, then the X driver uses the modes listed in the relevant "Display" subsection, attempting to place matching modes on each display device. Currently, the only token that requires a parentheses-enclosed value is "Transform". When used in conjunction with stereo mode "4", this allows each display to be configured independently to show any stereo eye.
If the X screen is not configured for stereo mode "4", these options are ignored. See Option "Stereo" "integer" for more details about stereo configurations.
Possible values are "0" with synonyms "no", "off" and "normal" , "90" with synonyms "left" and "CCW" , "" with synonyms "invert" and "inverted" and "" with synonyms "right" and "CW". Independent rotation configurability of each display device is also possible through RandR. Possible values are "X", "Y" and "XY". Independent reflection configurability of each display device is also possible through RandR.
This is equivalent to the transformation matrix specified through the RandR 1. As in RandR, the transform is applied before any specified rotation and reflection values to compute the complete transform. The 3x3 matrix is represented in the MetaMode syntax as a comma-separated list of nine floating point values, stored in row-major order. This is the same as the value passed to the xrandr 1 '--transform' command line option. Note that the transform value must be enclosed in parentheses, so that the commas separating the nine floating point values are interpreted correctly.
The region of the mode outside the ViewPortOut will contain black. This is useful, for example, for configuring overscan compensation.
0コメント