Commit 584638fa authored by 157.24.24.192's avatar 157.24.24.192
Browse files

abstract

parent 68c33889
= Introduction to Multiple Monitors in X =
This article explains the basic concepts and terms related to monitors and graphics cards in the X11 world. You need to know these terms, if you ever need help with a multi-monitor environment. For actual configuration tutorials, see the links on [[Randr12|RandR 1.2]] page.
== The X Protocol Screen ==
The most important concept in understanding how X deals with multiple monitors is the X protocol screen. This page refers to it as SCREEN. Traditionally in X11, a SCREEN had a one-to-one correspondence with a physical display device (a monitor). Dual- or multi-head graphics cards did not really exist, and things were simple. The X configuration file ({{{xorg.conf}}}) has one {{{Section "Screen"}}} for each SCREEN, either explicitly written in the file, or nowadays implicitly created by the X server.
The most important concept in understanding how X deals with multiple monitors is the X protocol screen. This article refers to it as SCREEN. Traditionally in X11, a SCREEN had a one-to-one correspondence with a physical display device (a monitor). Dual- or multi-head graphics cards did not really exist, and things were simple. The X configuration file ({{{xorg.conf}}}) has one {{{Section "Screen"}}} for each SCREEN, either explicitly written in the file, or nowadays implicitly created by the X server.
SCREENs are independent. They can have, not only different video modes, but also different color depths and resolution (dots-per-inch, used in scaling e.g. true-type fonts). Windows can never span more than one SCREEN, nor can they be moved from one SCREEN to another. The only way (that your author knows about) to switch focus from one SCREEN to another is with the mouse. Internally, each SCREEN is driven by a separate driver (DDX) instance, since SCREENs had one-to-one correspondence with graphics cards, too.
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment