Re: [PATCH] Add hybrid full-size/empty-clip mode to SetRootClip

Hi Daniel, - Original Message - > [Accidentally sent the unannotated version - sorry.] > > Hi, > > On 23 November 2015 at 07:51, Olivier Fourdan wrote: > > diff --git a/hw/xwayland/xwayland-output.c b/hw/xwayland/xwayland-output.c > > index 5ef444d..2a180f2 100644

Re: [PATCH] Add hybrid full-size/empty-clip mode to SetRootClip

Hi Daniel, - Original Message - > I'm not a big fan of the Bool -> int -> enum trickery > but I'm not sure if we could afford to have an enum > without breaking API/ABI (although I reckoned most compilers > would use an int for an enum, no?), but if we have no other > choice then, fine.

Re: [PATCH] Add hybrid full-size/empty-clip mode to SetRootClip

Hi Olivier, On 8 February 2016 at 16:00, Olivier Fourdan wrote: >> Tested by starting with a single output, manually checking >> screenInfo.screens[0]->root->{winSize,borderSize,borderClip,clipList} >> with gdb, hotplugging an output, verifying the regions again and also >>

Re: [PATCH] Add hybrid full-size/empty-clip mode to SetRootClip

Hi Daniel, - Original Message - > [Accidentally sent the unannotated version - sorry.] > [...] > > Unfortunately this totally breaks output hotplug, regressing the fix > from 216bdbc735. The effect is that if you hotplug an output and move an > XWayland window on to it, it can never