On Fri, Jan 11, 2013 at 01:50:45PM +0300, Vasily Khoruzhick wrote:
> Signed-off-by: Vasily Khoruzhick
Yeah, it's all a bit messy, but this is better.
Kristian
> ---
> src/gl-renderer.h | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/src/gl-renderer.h b/src/gl-
On Tue, Jan 15, 2013 at 09:48:55PM +0100, Jonas Ådahl wrote:
> On Tue, Jan 15, 2013 at 9:44 PM, Kristian Høgsberg
> wrote:
> > On Tue, Jan 15, 2013 at 09:25:56PM +0100, Jonas Ådahl wrote:
> >> To be able to have a fullscreen surface on one output, and interact with
> >> surfaces on another output
On Tue, Jan 15, 2013 at 9:44 PM, Kristian Høgsberg wrote:
> On Tue, Jan 15, 2013 at 09:25:56PM +0100, Jonas Ådahl wrote:
>> To be able to have a fullscreen surface on one output, and interact with
>> surfaces on another output, don't lower the fullscreen layer on
>> activate.
>
> This breaks alt-t
On Tue, Jan 15, 2013 at 09:25:56PM +0100, Jonas Ådahl wrote:
> To be able to have a fullscreen surface on one output, and interact with
> surfaces on another output, don't lower the fullscreen layer on
> activate.
This breaks alt-tab on single-output configurations. The idea is that
you can alt-t
On Tue, Jan 15, 2013 at 09:25:55PM +0100, Jonas Ådahl wrote:
> The input region of the black surface placed under the fullscreen shell
> surface did not have a specified input region. Because the initial input
> region of a surface is infinity, no other surface on any other output
> could get any f
To be able to have a fullscreen surface on one output, and interact with
surfaces on another output, don't lower the fullscreen layer on
activate.
Signed-off-by: Jonas Ådahl
---
src/shell.c |1 -
1 file changed, 1 deletion(-)
diff --git a/src/shell.c b/src/shell.c
index cdbb756..47882a5 100
The input region of the black surface placed under the fullscreen shell
surface did not have a specified input region. Because the initial input
region of a surface is infinity, no other surface on any other output
could get any focus.
Signed-off-by: Jonas Ådahl
---
src/shell.c |2 ++
1 file
On Sun, Jan 13, 2013 at 03:51:26AM -0300, Diego Viola wrote:
> ---
> architecture.html | 10 +-
> building.html | 6 +++---
> faq.html | 10 +-
> index.html| 4 ++--
> toolkits.html | 2 +-
> xserver.html | 6 +++---
> 6 files changed, 19 insertion
Hi all,
I'm getting to a point where I can't keep track of which patches and
series are out there pending review/commit/etc. Two weeks of holiday
and then catching up on email and various paper work pushed me over
the edge. I used to have a list locally of patches I needed to get
back to, but it
On Fri, Jan 11, 2013 at 09:01:47PM -0600, Jason Ekstrand wrote:
> Add a destroy signal to the wl_event_loop object.
>
> ---
> Again, this helps me prevent memory leaks.
>
> This time I used tabs ;-)
Applied, with just a couple of tweaks to the commit message:
- subject line doesn't end with a
On Mon, Jan 14, 2013 at 09:34:34PM -0600, Jason Ekstrand wrote:
> Wayland devs:
> A few weeks ago, I sent out a proposal on how we could extend the current
> Wayland API to allow for more general event and request dispatching. I
> finally
> got around to talking to Kristian about it and some of t
Hi Vasily
On Tue, Jan 15, 2013 at 4:13 PM, Vasily Khoruzhick wrote:
> On Tue, Jan 15, 2013 at 5:08 PM, Philip Withnall
> wrote:
>> This is an initial version of an fbdev backend for Weston. I don't
>> consider it polished; I'm just looking for rough feedback at the
>> moment. The work is also a
On Tue, Jan 15, 2013 at 5:08 PM, Philip Withnall wrote:
> This is an initial version of an fbdev backend for Weston. I don't
> consider it polished; I'm just looking for rough feedback at the
> moment. The work is also available as a gitorious branch if anyone
> prefers that:
> https://gitorious.o
This is an initial version of an fbdev backend for Weston. I don't
consider it polished; I'm just looking for rough feedback at the
moment. The work is also available as a gitorious branch if anyone
prefers that:
https://gitorious.org/~pwithnall/weston/pwithnalls-weston/commits/compositor-fbdev
On
On Mon, 14 Jan 2013 21:34:34 -0600
Jason Ekstrand wrote:
> Wayland devs:
> A few weeks ago, I sent out a proposal on how we could extend the current
> Wayland API to allow for more general event and request dispatching. I
> finally
> got around to talking to Kristian about it and some of the AB
15 matches
Mail list logo