Re: 1.2a6 bug: Doesn't handle display config changes
Re: 1.2a6 bug: Doesn't handle display config changes
- Subject: Re: 1.2a6 bug: Doesn't handle display config changes
- From: Ben Byer <email@hidden>
- Date: Wed, 07 Nov 2007 02:37:49 -0800
On Nov 6, 2007, at 6:48 PM, Mark J. Reed wrote: On 11/6/07, Ben Byer <email@hidden> wrote:
On Nov 6, 2007, at 11:07 AM, Nathaniel Gray wrote:
On Nov 5, 2007 5:10 PM, Mark J. Reed <email@hidden> wrote:
Is the xrandr command available?
I tried it, but it complains that the RANDR extension isn't supported.
Bummer. IIRC it should be. The output of config.log says that it
enabled ("#define RANDR 1"), but the output of xdpyinfo doesn't report
it as a supported extension. Odd..
Maybe it's supported in the X server but not in the video driver?
Although I'd love the luxury of blaming someone else, we don't actually *have* video drivers -- we just talk to Quartz / CoreGraphics. If your Mac reacts at all when you plug another monitor in, then the OS X video driver is working correctly. CoreGraphics is then supposed to give us a notification that the display has changed -- probably via Xplugin -- and then we need to use RANDR to act on that.
I'm going to assume that CG is in fact giving us the notification, and that this is a bug in Xquartz (we're not listening for the right notification). Please file a bug, if you haven't already. -- Ben Byer CoreOS / BSD Technology Group, XDarwin maintainer
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden