Re: Same ilm surface on multiple layer support

Hi Wataru, I have tried it and unfortunately it do not solve the issue. Is it known issue or it is happening due to older (1.11.0) version of weston and ivi which i am using. Best Regards, Vikash On Thu, May 10, 2018 at 3:54 PM, Mizuno, Wataru (ADITJ/SWG) < wmiz...@jp.adit-jv.com> wrote: > Hi

[PATCH libinput] meson: add a 'coverity' option to fix the build

Coverity screwed up something so we can't submit builds right now, the compilation units all fail. math.h pulls in a _Float128 type that coverity cannot handle. So as a workaround, add an option to the build to avoid this and remove it when the next version of coverity hopefully fixes this.

Re: [writing a compositor] wl_display_add_socket_auto fails

As I know, if it failed to lock lock file in wl_socket_lock(), it returns a negative value and wl_display_add_socket_auto() will continue to try to add socket with increased display number. In your case, it will try to create socket with wayland-1. Please check your compositor running with

[writing a compositor] wl_display_add_socket_auto fails

I am attempting to write a test compositor using libweston. I want to run it in a window on GNOME Shell, so I am using the Wayland backend. When I call wl_display_add_socket_auto, it fails with the error message: unable to lock lockfile /run/user/1000/wayland-0.lock, maybe another compositor is

Re: libinput varlink implementation?

On Thu, May 10, 2018 at 08:34:56PM -0400, Drew DeVault wrote: > Does it make more sense to make libinput provide this information in a > structured/predictable way via its log callback, then pull that out of > compositor logs? I've just done something like this to debug pointer acceleration in

Re: libinput varlink implementation?

Does it make more sense to make libinput provide this information in a structured/predictable way via its log callback, then pull that out of compositor logs? ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org

Re: libinput varlink implementation?

So we don't cross the streams, some motivation is in the reply to Drew, https://lists.freedesktop.org/archives/wayland-devel/2018-May/038148.html I'll try to avoid duplication of those points here. On Thu, May 10, 2018 at 10:10:10AM +0200, Markus Ongyerth wrote: > A quick glance at varlink makes

Re: libinput varlink implementation?

On Thu, May 10, 2018 at 08:23:31AM -0400, Drew DeVault wrote: > Can you be more specific about your use-case? As far as I can tell, you > want to find out how the devices were configured by the compositor. On > sway this is as straightforward as reading sway's debug log. > > I guess I'm not clear

Re: [PATCHv4 wayland-protocols] text-input: Add v3 of the text-input protocol

On Thu, May 10, 2018 at 11:46:32AM +0200, Dorota Czaplejewicz wrote: > On Thu, 10 May 2018 11:43:12 +0200 > Dorota Czaplejewicz wrote: > > > On Tue, 08 May 2018 07:07:24 + > > Silvan Jegen wrote: > > > > > On Mon, May 7, 2018 at 5:11 AM

Re: libinput varlink implementation?

Can you be more specific about your use-case? As far as I can tell, you want to find out how the devices were configured by the compositor. On sway this is as straightforward as reading sway's debug log. I guess I'm not clear on why a more complex solution is necessary. -- Drew DeVault

RE: Same ilm surface on multiple layer support

Hi Vikas, This issue might be fixed with this patch: e8ff7df863a10eb4be5273017fb544b5f823fc6a Please try with it. Best regards, Wataru Mizuno ADITJ / SWG +81-(0)566-56-0946 From: Vikas Patil [mailto:vikasmpa...@gmail.com] Sent: Thursday, May 10, 2018 4:07 PM To: Ucan, Emre (ADITG/ESB) Cc:

RE: Same ilm surface on multiple layer support

Hi Vikas, This issue might be fixed with this patch: e8ff7df863a10eb4be5273017fb544b5f823fc6a Please try with it. Best regards, Wataru Mizuno ADITJ / SWG +81-(0)566-56-0946 From: Vikas Patil [mailto:vikasmpa...@gmail.com] Sent: Thursday, May 10, 2018 4:07 PM To: Ucan, Emre (ADITG/ESB) Cc:

Re: [PATCHv4 wayland-protocols] text-input: Add v3 of the text-input protocol

On Thu, 10 May 2018 11:43:12 +0200 Dorota Czaplejewicz wrote: > On Tue, 08 May 2018 07:07:24 + > Silvan Jegen wrote: > > > On Mon, May 7, 2018 at 5:11 AM Joshua Watt wrote: > > > IMHO, if you are doing UTF-8 (which

Re: [PATCHv4 wayland-protocols] text-input: Add v3 of the text-input protocol

On Tue, 08 May 2018 07:07:24 + Silvan Jegen wrote: > On Mon, May 7, 2018 at 5:11 AM Joshua Watt wrote: > > IMHO, if you are doing UTF-8 (which you should), you should *always* > > specify any offset in the string as a byte offset. I have a few > >

Re: libinput varlink implementation?

A quick glance at varlink makes me like it more than dbus, but I'm not sure it's the best choice to provide debug information about libinput configuration in compositors. All compositors I'm aware of, provide an IPC method for some (more or less) internals. GNOME (and afaik KDE) have dbus,

[PATCH weston] Fix a crash when unlocking or unconfining a pointer

In GNOME (but not in Weston), if a window loses focus, the client first receives the focus event, then the unlock/unconfine event. This causes toytoolkit to dereference a NULL window when unlocking or unconfining the pointer. To repro: - Run weston-confine - Click the window - Alt-Tab away from

Re: Same ilm surface on multiple layer support

Hi All, As some of the LayerManagerControl commands do not work when same surface is attached to two layers. Following command hangs and do not come out as expected. I tried to check where it is hanging using GDB. Is this gives some hit on issue and resolution? Please suggest if you have any

Re: [PATCH libinput] test: check if tapping that happens after a moving thumb works

On Thu, May 10, 2018 at 12:47:33AM +0200, Friedrich Schöller wrote: > --- > test/test-touchpad.c | 40 > 1 file changed, 40 insertions(+) > > diff --git a/test/test-touchpad.c b/test/test-touchpad.c > index b73d9e58..8341e209 100644 > ---