We get the child position but never use this information here. Just remove it.
Spotted by Christopher Michael.
Signed-off-by: Stefan Schmidt s.schm...@samsung.com
---
src/xwayland/window-manager.c |2 --
1 file changed, 2 deletions(-)
diff --git a/src/xwayland/window-manager.c
Signed-off-by: Stefan Schmidt s.schm...@samsung.com
---
clients/.gitignore |1 +
1 file changed, 1 insertion(+)
diff --git a/clients/.gitignore b/clients/.gitignore
index aa5e53c..23959cc 100644
--- a/clients/.gitignore
+++ b/clients/.gitignore
@@ -41,6 +41,7 @@ weston-screensaver
Hello.
Ignore the 7 in the patchset count its only these two patches.
regards
Stefan Schmidt
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
How and when to update the keymap is left to each backend.
The new keymap only becomes effective when no keys are pressed and we
keep latched and locked modifiers from the previous state.
---
v2:
- defer updating the keymap until no keys are pressed;
- keep latched and locked modifiers state;
---
src/compositor-wayland.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/src/compositor-wayland.c b/src/compositor-wayland.c
index 77b2a2c..0fd7267 100644
--- a/src/compositor-wayland.c
+++ b/src/compositor-wayland.c
@@ -515,7 +515,11 @@ input_handle_keymap(void
---
clients/window.c | 24 +++-
1 file changed, 15 insertions(+), 9 deletions(-)
diff --git a/clients/window.c b/clients/window.c
index 5b20da5..1f32c73 100644
--- a/clients/window.c
+++ b/clients/window.c
@@ -3037,6 +3037,8 @@ keyboard_handle_keymap(void *data, struct
Hi,
On 7 October 2013 16:27, Daniel Stone dan...@fooishbar.org wrote:
But I'm really not sure about this. It's really hard to get this
right, especially when you're changing modifier options. The only
real workable solution I've seen is to pend the actual change until
all keys have been
Hi,
On 7 October 2013 20:16, Ran Benita ran...@gmail.com wrote:
At least retaining the locked modifiers (and therefore the LED state in
most cases) would be nice, and not too problematic I think (though some
edge cases are expected).
Ok, the new version keeps both latched and locked
On Thu, Oct 10, 2013 at 07:53:12PM +0200, Rui Tiago Cação Matos wrote:
Hi,
On 7 October 2013 20:16, Ran Benita ran...@gmail.com wrote:
At least retaining the locked modifiers (and therefore the LED state in
most cases) would be nice, and not too problematic I think (though some
edge
Hi all,
I've tagged and pushed the 1.3 release and it's available from
http://wayland.freedesktop.org/releases as usual and the hashes for
this release are:
febbbfc8d76ed0b2157077d50cb6e5ceb1aa47de wayland-1.3.0.tar.xz
2c3dbb89031f120fb191492634e53a583f99d57d wayland 1.3.0 tag
On Wed, Oct 09, 2013 at 11:29:45AM +0200, Tomeu Vizoso wrote:
---
src/rpi-renderer.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Thanks, applied to master. We're not not branched yet, so this will
apply to both 1.3.1 and 1.4.
Kristian
diff --git a/src/rpi-renderer.c
On Wed, Oct 09, 2013 at 11:30:57AM +0200, Tomeu Vizoso wrote:
---
src/launcher-util.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
Thanks, applied to master.
Kristian
diff --git a/src/launcher-util.c b/src/launcher-util.c
index 6c28dc3..8b19b9d 100644
---
12 matches
Mail list logo