On Fri, Oct 26, 2012 at 08:33:04PM +0200, Marco wrote: > 2012-10-26 Uli Schlachter: > > But people wanted to move windows between screens, so Xinerama is > > created. To 'old' clients, Xinerama looks like a single, big > > protocol screen. However, only parts of it are visible. You can > > ask the Xinerama extension for which parts exactly are visible. > > > > Then came RANDR. RANDR doesn't really matter to this issue at all. > > It just made dynamic configuration possible. With Xinerama, you > > had to configure the layout before starting the server. RANDR > > makes it possible to enable new screens at runtime. > > I assume that the -s setting of xcalib operates on the "protocol > screen", the I don't understand why only one screen is inverted, > since they both belong to the same protocol screen. If RANDR uses > the same screen notion as Xinerama it also should invert both, since > both appear as a single one.
(pure IMHO) Well, if I remember right VidMode is as ancient as X11 itself. As RANDR was patched in later, and allowed to mix physical outputs to one "protocol screen" there still needed to be a way to calibrate each output for itself. So I guess one has to either create a ICC profile that does the inversion for each monitor and use some of the screen calibration utilities to load it (probaply not xcalib ;) or port xcalib's invert function to a single tool that runs again RANDR (maybe redshift might be a good example). > > If I understand this correctly, then I didn't even know that X11 > > can do so. I never heard about xcalib either (and I haven't ever > > built and run xcalib). > > When I heard about the possibility if inverting a screen (or a > single window) I thought of it as a useless cheap gimmick. But once > discovered I have to admit that inverting is a very handy small > tool. I have two use-cases: > > ∙ insane web designers which print white text on black background > (often combined with a very thin font) Understandable for me ;) at least the other way round. I hate websites that use plain white (#FFFFFF) as background color, as usually I work and live at night, and this ruins my concentration and visual reception quality. > ∙ reading PDFs in a dark environment. Usually I set my PDF reader to > low-contrast (dark grey on light grey) for that, but some PDFs > use white as background and then the inversion comes into play. Well, to fix this work at night problem I'd really like to recommend redshift (for linux) and f.lux (for windows and mac os). It adjusts the color temperature of all outputs to a more night fitting red. So once you got used to seeing a slight red instead of white you will be much more relaxed over the night or in dark environments. And it also just "burns" the really bright colors, and doesn't make the dark onces totally unreadable. Regards, Andre
smime.p7s
Description: S/MIME cryptographic signature
