Kristian Høgsberg wrote:
The compositor is not going to discard part of the buffer like that.
If the window is fullscreen or maximized or maximized
vertically/horizontally, the client has to know that and render a
buffer that works for that window state.
If I drag a window so that a portion of
On Mon, Aug 13, 2012 at 1:20 PM, Bill Spitzak wrote:
>
>
> Kristian Høgsberg wrote:
>
>> That's a nice improvement indeed. I've committed it since it's
>> obviously a step forward, but I think we could use the input region
>> extents for placement. There's been talk of a outline region or such,
Kristian Høgsberg wrote:
That's a nice improvement indeed. I've committed it since it's
obviously a step forward, but I think we could use the input region
extents for placement. There's been talk of a outline region or such,
something to define the "edge" of the window for snapping and
plac
On Mon, Aug 13, 2012 at 02:07:52PM +0100, Rob Bradford wrote:
> From: Rob Bradford
>
> Place the window in a random position on the output where the first seat with
> a pointer is. When calculating the random position limit the range to the
> area that would ensure that the whole surface is visib
From: Rob Bradford
Place the window in a random position on the output where the first seat with
a pointer is. When calculating the random position limit the range to the
area that would ensure that the whole surface is visible. If the surface is
larger than the output then the surface is placed
From: Rob Bradford
Place the window in a random position on the output where the first seat with
a pointer is. When calculating the random position limit the range to the
area that would ensure that the whole surface is visible. If the surface is
larger than the output then the surface is placed
