Re: [AD] More X Mode Setting

[Peter Wang <novalazy@xxxxxxxxxx>]

On 2011-01-12, Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx> wrote:
> 
> I'm in the middle of refactoring the XRandR code. Not entirely sure when it'll 
> be done (soonish), but it is necessary.
> 
> Seems XRandR doesn't do anything without you telling it, and doesn't have any 
> notion about what relation one monitor is to the next, ie: theres no LeftOf or 
> Above type flags, so we have to calculate the right monitor origins for each 
> set of modes, to make sure multiple full screen displays are right next to 
> each other. And re-querying Xrandr can be a tad expensive so I've added in the 
> code to handle XRR notify events. But it turns out it'll be more efficient to 
> store our own custom XRR structures rather than pointing to XRROutput 
> structures, this way we'll be able to detect what exactly changed (the change 
> events in XRR are rather coarse, just tells you that a CRTC or Output changed, 
> and not what inside changed).

I don't know if it would help you, but reconfiguring monitor setups is
not something people do very often (if ever), so efficiency isn't a high
priority.

> If I'm able to work on it solid for the next couple days, I can see it being 
> done this weekend for sure. That includes a bunch of testing.
> 
> I really do wish the system vtable had a separate entry for creating a 
> fullscreen display. Would make the xdpy_create_display function[s] much 
> simpler and cleaner.

We can consider it for 5.1.

> All this extra time has let me figure out some funny things about X and WMs 
> though. Like we should NOT apply the PSize size hints to full screen windows, 
> and a few other funny things. But I'll have to retest them to be sure it 
> wasn't just the size hints getting set messing stuff up (it seems to confuse 
> most WMs to no end, with full screen windows).

Ok, thanks.

Peter
Allegro project manager (self-appointed)