---
src/shell.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/shell.c b/src/shell.c
index 2b61202..482c9b8 100644
--- a/src/shell.c
+++ b/src/shell.c
@@ -1176,7 +1176,7 @@ zoom_grab_key(struct wl_keyboard_grab *grab,
struct weston_output *output;
s
It is my understanding that games wanting uninhibited input events will end
up reading raw input data directly.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Hi,
On 3 March 2012 15:48, Scott Moreau wrote:
> Clients shouldn't attempt to track modifier state independently
> since it's already tracked in the modifier mask.
NAK - games want to use Ctrl/Alt to shoot, and so on. But they're
right that they shouldn't try to independently track the state.
Hi Alberto,
I have updated the wayland moduleset in jhbuild according to the latest
build instructions on the wayland website. This includes adding libxcb
from git and xorg dri2proto. A number of configure options were enabled
but the weston install-setuid option was disabled.
Would you mind chec
---
src/util.c | 14 --
1 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/src/util.c b/src/util.c
index 3ca940f..491516e 100644
--- a/src/util.c
+++ b/src/util.c
@@ -240,8 +240,18 @@ weston_compositor_run_binding(struct weston_compositor
*compositor,
wl_list_fo
Clients shouldn't attempt to track modifier state independently
since it's already tracked in the modifier mask.
---
clients/window.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/clients/window.c b/clients/window.c
index e917ce6..538571e 100644
--- a/clients/window.c
+