RE: Question about multi-displays control on wayland protocol‏

2014-10-10 Thread Yang Andy
Hi Pekka Thank you very much for your reply. >It would definitely be easier if you only need one EGLDisplay, and >can use the EGLNativeWindowType argument of eglCreateWindowSurface() to >choose the target output for the EGLSurface. In this case the required >modifications would be limited to you

Re: [PATCH weston] input: don't send to clients key events eaten by bindings

2014-10-10 Thread Bill Spitzak
The client will do some kind of check to see if the space key is down. This should resemble as much as possible a round trip to actually see if the key is pressed on the hardware. I figured this involved peeking into the xkb structure to see what keys are held down. "some kind of check". Making

[PATCH weston] input: fix access to invalid resource

2014-10-10 Thread Giulio Camuffo
the keyboard focus surface may not have a valid resource (server side surface or a surface surviving its client), so check if it is valid before using it. --- src/input.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/input.c b/src/input.c index e765221..bc58223 100644 ---

Re: [PATCH weston] input: don't send to clients key events eaten by bindings

2014-10-10 Thread Giulio Camuffo
2014-10-10 23:11 GMT+03:00 Bill Spitzak : > On 10/10/2014 11:41 AM, Giulio Camuffo wrote: > >> Ok, so let's change the example. Space doesn't switch the active >> window, but toggles the speaker mute. So hitting space will not send a >> key event to the client, which will not know space is pressed,

Re: [PATCH weston] input: don't send to clients key events eaten by bindings

2014-10-10 Thread Bill Spitzak
On 10/10/2014 11:41 AM, Giulio Camuffo wrote: Ok, so let's change the example. Space doesn't switch the active window, but toggles the speaker mute. So hitting space will not send a key event to the client, which will not know space is pressed, so your nice space+x shortcut won't work. Yes thi

[PATCH libinput] tablet: Normalization functions can return 1.0

2014-10-10 Thread Bill Spitzak
--- src/evdev-tablet.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/evdev-tablet.c b/src/evdev-tablet.c index ff5f737..9921823 100644 --- a/src/evdev-tablet.c +++ b/src/evdev-tablet.c @@ -105,7 +105,7 @@ tablet_update_tool(struct tablet_dispatch *tablet, static

Re: [PATCH weston] input: don't send to clients key events eaten by bindings

2014-10-10 Thread Giulio Camuffo
Oh, i didn't realize we dropped the ML. adding again. 2014-10-10 21:17 GMT+03:00 Bill Spitzak : > On 10/09/2014 11:42 PM, giuliocamu...@gmail.com wrote: > >>> Are you proposing something else? >> >> >> IsSpaceKeyDown() should always return false. >> What I'm looking for here is consistent behaviou

Re: [PATCH v3 1/2] Protocol: Add destructor to wl_data_device interface Fix for Bug# 81745

2014-10-10 Thread Giulio Camuffo
2014-09-22 12:28 GMT+03:00 Pekka Paalanen : > On Wed, 27 Aug 2014 16:33:25 +0530 > kabeer.k...@samsung.com wrote: > >> From: kabeer >> >> Signed-off-by: kabeer >> --- >> protocol/wayland.xml | 11 +-- >> 1 file changed, 9 insertions(+), 2 deletions(-) >> >> diff --git a/protocol/waylan

Re: [PATCH weston v4] Implement data_device interface destructor

2014-10-10 Thread Giulio Camuffo
A could of comments below, the rest looks good to me. 2014-09-23 8:21 GMT+03:00 kabeer khan : > window : compare version and call appropriate destructor > data-device : change version of creation of data_device_manager and > data_device interfaces Maybe it would be better to split these two cha

Re: Gstwaylandsink - Createwindow

2014-10-10 Thread Daniel Stone
Hi, On 10 October 2014 15:30, Kishore Divvela -ERS, HCL Tech wrote: > I am trying play video with gst-launch-1.0 and waylandsink, everytime i > see the window is getting creating different position, how to set window > position? > Window positioning is controlled by the compositor, so you'll h

Re: Failing to add socket to wayland display.

2014-10-10 Thread Daniel Stone
Hi, On 10 October 2014 11:02, Srivardhan wrote: > stat = wl_display_add_socket(test_display, socket_name); > if (stat) > fprintf(stderr, "Successfully connected to wayland > display\n"); > else > fprintf(stderr, "Failed to connect to waylan

Gstwaylandsink - Createwindow

2014-10-10 Thread Kishore Divvela -ERS, HCL Tech
Hi, I am trying play video with gst-launch-1.0 and waylandsink, everytime i see the window is getting creating different position, how to set window position? Regards, Kishore ::DISCLAIMER::-

[PATCH weston] compositor: make keep_buffer a bool

2014-10-10 Thread Derek Foreman
The comments already call it bool, so let's just make it one --- src/compositor-drm.c | 4 ++-- src/compositor.h | 3 ++- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/src/compositor-drm.c b/src/compositor-drm.c index 07b83a7..bee41ef 100644 --- a/src/compositor-drm.c +++ b/sr

Re: Failing to add socket to wayland display.

2014-10-10 Thread Ryo Munakata
On Fri, 10 Oct 2014 15:32:54 +0530 Srivardhan wrote: > Hi, > > I wrote a small program to understand wayland-server. Below is the program: > #include > #include > > const char socket_name[] = "test_socket"; > > int main() > { > struct wl_display *test_display = NULL; > int st

Re: [PATCH weston] gl-renderer: don't move memory in output_rotate_damage

2014-10-10 Thread Jason Ekstrand
Looks good to me. Pushed. ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel

Failing to add socket to wayland display.

2014-10-10 Thread Srivardhan
Hi, I wrote a small program to understand wayland-server. Below is the program: #include #include const char socket_name[] = "test_socket"; int main() { struct wl_display *test_display = NULL; int stat = 0; test_display = wl_display_create(); if (test_display)

Re: [PATCH libinput] Fix normalization functions

2014-10-10 Thread Peter Hutterer
On Thu, Oct 09, 2014 at 10:28:54AM +0200, Hans de Goede wrote: > Hi, > > On 10/09/2014 12:56 AM, Bill Spitzak wrote: > > That certainly looks correct, but this code will return a value less than > > 1.0 when absinfo->value == absinfo->maximum. Is this correct? If it is > > supposed to be 1.0 the