3 ms·
Imagine you are sitting on a train in London with your friend on your way to work and you are having a conversation with your mom back in New York. Meanwhile yo
by michaelmrose 4y ago
Imagine you are sitting on a train in London with your friend on your way to work and you are having a conversation with your mom back in New York. Meanwhile your friend is loudly insisting that everyone knows that cellular connections can't cross oceans because cell towers just don't have that much range. He's sort of correct but he's missed the point.
Let me try again. Here is an xrandr invocation that configures 3 screens [1080P 24"][4K 27"][1080p 24"]
xrandr --dpi 163
--output HDMI-0 --mode 1920x1080 --scale 1.75x1.75 --pos 0x0
--output DP-4 --auto --pos 3360x0
--output DP-1 --mode 1680x1050 --scale 1.75x1.75 --pos 7200x0
One could simply run it at boot or better one can save the present configuration to xorg.conf. The nvidia-settings app both lets you do this with a GUI or can look what xrandr has set up and save THAT to your xorg.conf
If one simply runs xrandr after one sees a curious thing. The 1080 monitors are listed as being 3360x1890. If we pop out our calculator we will note that the systems sees every screen as being about 161 DPI. Prove it to yourself if you like.
https://www.sven.de/dpi/ https://www.sven.de/dpi/
This means that the most poorly written application on earth only has to contend with high dpi support not mixed DPI. X asks nothing of the client it needs no magic variables nor insight into its linked libraries or images. If you grasp the window metaphorically and move it from screen to screen its size won't perceptively flutter because the screen differential in DPI is as far as its concerned within 1%. If you open a fullscreen app it will draw its window to the whole perceptible 3360 width of the screen and X will scale it down to the actual width of 1920. X has taken sole responsibility for giving a fuck what the difference in DPI is. High DPI support at this point is very good and no scripts to "paper" over anything is required.
xrandr --scale is a thing that would have worked in 2003 and still works in 2022 even if people have forgotten about it.