2012-10-26 Uli Schlachter: > Looking at the xcalib source code, it uses the XF86VidMode extension to mess > with stuff. There are no monitors specified here, so... dunno. From the code, > I > would have guessed that this applies to all monitors, but the X11 server seems > to think otherwise.
Thanks for digging into the sources for me. You can also find out if you try to run xcalib on an Xserver without XF86VidMode, it yells Xlib: extension "XF86-VidModeExtension" missing on display ":0.0". Error - Unable to query gamma ramp size > The -s option let's you specify the screen to use. In theory. This uses X11's > zaphod mode. In this mode, you cannot move windows between screens. For this > reason, since Xinerama, there is always just a single, big, virtual screen on > the display and the individual monitors are handled otherwise. That's unfortunate. Selecting the screen is exactly what I need and the tool supports it. And it still doesn't work. Just for clarification: there are two different, exclusive notions of a screen, right? - screen (which works with Xinerama, but not xrandr) - screen (awesome/xrandr notion of screen) Since both are different things (correct me if I'm wrong) is there a term to correctly identify either one? How does the Xserver call them? Or does the Xserver have no clue about the awesome screen? > TL;DR: I have no clue about XF86VidMode, but I guess it doesn't let you do > what > you want. Given that inversion is such a simple and basic operation, I wonder if there's likewise a simple solution (I already tried to flip over my monitor cable, but it won't fit ;). Marco -- To unsubscribe, send mail to [email protected].
