Signed-off-by: Jonas Ådahl jad...@gmail.com
---
Hi,
Haven't tested this on a clickpad, but it should disable the tapping
feature for clickpads and other touchpads that advertise the existance
of a buttonpad.
Jonas
src/evdev-touchpad.c | 17 +
1 file changed, 17 insertions(+)
On Wed, 20 Mar 2013 22:06:22 -0600
Scott Moreau ore...@gmail.com wrote:
Hi Jason,
On Wed, Mar 20, 2013 at 7:56 PM, Jason Ekstrand ja...@jlekstrand.net wrote:
There is one more question that I think needs to be answered. And
that is: do we handle things in terms of set/unset or in terms
On Wed, 20 Mar 2013 13:09:48 -0400
Jerome Glisse j.gli...@gmail.com wrote:
On Wed, Mar 20, 2013 at 4:32 AM, RenoX reno...@gmail.com wrote:
On Tue, Mar 19, 2013 at 11:34 AM, Jason Ekstrand ja...@jlekstrand.net
wrote:
I'm not sure exactly what I think of all this surface transform
On Mon, 18 Mar 2013 21:43:32 +0100
Hardening rdp.eff...@gmail.com wrote:
On 18/03/2013 13:48, Uli Schlachter wrote:
Hi,
On 18.03.2013 00:30, Hardening wrote:
On 17/03/2013 23:59, Sylvain BERTRAND wrote:
On Sun, Mar 17, 2013 at 11:32:21PM +0100, Hardening wrote:
This patch adds a
From: Rob Bradford r...@linux.intel.com
Provide a definition of EGL_BUFFER_AGE_EXT so that you can compile against an
EGL stack that may not yet support that extension.
---
src/weston-egl-ext.h | 4
1 file changed, 4 insertions(+)
diff --git a/src/weston-egl-ext.h b/src/weston-egl-ext.h
On Fri, Mar 22, 2013 at 02:15:49PM +, Rob Bradford wrote:
From: Rob Bradford r...@linux.intel.com
Provide a definition of EGL_BUFFER_AGE_EXT so that you can compile against an
EGL stack that may not yet support that extension.
---
src/weston-egl-ext.h | 4
1 file changed, 4
This patch implements a popup stack. When the first popup is opened
the grab is started, and it is added to a list. Further popups will
be added to this list but the grab won't change. When a popup is
closed it is removed from the list and, if it is now empty, the grab
is ended.
A click outside
Hi,
Here's another release in the 1.0 series and this time I really think
it's going to be the last one from the 1.0 branch. We'll release 1.1
so and as the 1.0 and master branches diverge, it becomes harder and
harder to cherry-pick fixes from master.
On the wayland side it's mainly Jonas
Hi Jonas,
I'm really starting to like the look of this. However there are
still a few sticky spots. First: How do you plan to handle resizing in
a sane way? Do you plan to do that entirely through the external IPC
mechanism or have some sort of configure event that gets passed via
wayland?
From: U. Artie Eoff ullysses.a.e...@intel.com
Fixes https://bugs.freedesktop.org/show_bug.cgi?id=61997
Signed-off-by: U. Artie Eoff ullysses.a.e...@intel.com
---
src/compositor.c | 29 +
src/compositor.h | 7 ++-
src/evdev.c | 2 +-
3 files changed, 32
Wayland Devs,
After digging further into what this would actually imply, it looks
like the cascade of changes that would be required isn't worth it.
While this may happen in the distant future, we're not going to take
away wl_resource just yet. Specifically, EGL relies on it and
changing it right
On Fri, 22 Mar 2013 10:41:00 -0400
Jerome Glisse j.gli...@gmail.com wrote:
On Fri, Mar 22, 2013 at 6:35 AM, Pekka Paalanen ppaala...@gmail.com wrote:
On Wed, 20 Mar 2013 13:09:48 -0400
Jerome Glisse j.gli...@gmail.com wrote:
On Wed, Mar 20, 2013 at 4:32 AM, RenoX reno...@gmail.com wrote:
Hi Pekka, thanks for your comments here.
Scott,
do you mean that these unminimize, unmaximize, etc. requests would
actually work like undo? Unmaximize would undo what the last
maximization did, as opposed to just set_normal which might do
something slightly different since its aim is to
The underlying problem is that if a window is full-screen or maximized,
and you minimize it, then un-minimize should put it back to full-screen
or maximized. Thus un-minimize cannot be the normal state.
The compositor could track the previous state and set that but then the
client can't
Jonas Ådahl wrote:
There are two clients (A and B) that can communicate via some IPC
mechanism where A is the main process and B is a render process. B
renders to a surface and A decides its visibility and position. Below
follows an example how foreign surfaces can be used.
1. Both A and B
On Fri, Mar 22, 2013 at 7:09 PM, Bill Spitzak spit...@gmail.com wrote:
The underlying problem is that if a window is full-screen or maximized, and
you minimize it, then un-minimize should put it back to full-screen or
maximized. Thus un-minimize cannot be the normal state.
The compositor
16 matches
Mail list logo
