Re: [PATCH libinput] Add right click drag

Apologies for the long delay, I had to catch up with too many things and was stuck on some other bug for longer than I though. On Wed, Aug 23, 2017 at 12:07:15AM +0200, Corentin Marciau wrote: > Hi, > > For what it's worth, here is a patch of the touchpad tap state machine to > handle right

[PATCH 3/6] launcher-logind: only get a VT on seat0, as only seat0 supports VTs

--- libweston/launcher-logind.c | 22 -- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/libweston/launcher-logind.c b/libweston/launcher-logind.c index a069bd4f..11627590 100644 --- a/libweston/launcher-logind.c +++ b/libweston/launcher-logind.c @@ -762,18

[PATCH 5/6] libweston: fbdev: Attempt to detect the first framebuffer device in the seat, instead of defaulting to /dev/fb0

--- libweston/compositor-fbdev.c | 35 +-- 1 file changed, 33 insertions(+), 2 deletions(-) diff --git a/libweston/compositor-fbdev.c b/libweston/compositor-fbdev.c index a9cc08be..99362b8a 100644 --- a/libweston/compositor-fbdev.c +++

[PATCH 1/6] libweston: set the seat automatically based on the XDG_SEAT environment variable

--- compositor/main.c| 2 +- libweston/compositor-drm.c | 5 + libweston/compositor-fbdev.c | 5 + man/weston-drm.man | 7 +-- 4 files changed, 16 insertions(+), 3 deletions(-) diff --git a/compositor/main.c b/compositor/main.c index 0615d87e..61bda282 100644

[PATCH 4/6] libweston: fbdev: set fb device info upon the first run. This attempts to wake up secondary framebuffer devices (/dev/fb1 and up) as usually these devices start powered off, and the FBIOPU

-vga none -device VGA,id=video0 -device secondary-vga,id=video1 \ -device secondary-vga,id=video2 --- libweston/compositor-fbdev.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/libweston/compositor-fbdev.c b/libweston/compositor-fbdev.c index b4f0685c..a9cc08be 100644 ---

[PATCH 2/6] libweston: fbdev: support the --seat option, (and XDG_SEAT variable)

--- compositor/main.c| 2 ++ libweston/compositor-fbdev.c | 5 - libweston/compositor-fbdev.h | 1 + 3 files changed, 7 insertions(+), 1 deletion(-) diff --git a/compositor/main.c b/compositor/main.c index 61bda282..f88608cd 100644 --- a/compositor/main.c +++ b/compositor/main.c

[PATCH 6/6] main: don't configure /dev/fb0 by default

--- compositor/main.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/compositor/main.c b/compositor/main.c index f88608cd..cd07a6bb 100644 --- a/compositor/main.c +++ b/compositor/main.c @@ -1450,9 +1450,6 @@ load_fbdev_backend(struct weston_compositor *c,

Re: Why isn't Xwayland just a Wayland client?

Thank you Olivier! As I understand it, Wayland compositors are already compositing window managers. What aspect requires working outside of the protocol in this case? Absolute positions? Thanks again, Joseph On Tue, Sep 5, 2017 at 8:51 PM, Olivier Fourdan wrote: > Hi, > >

Re: Why isn't Xwayland just a Wayland client?

Hi, Xwayland is basically an X server, like any X server, it requires an X11 Window manager for the users to manipulate the windows on screen (size, location, stacking etc.) And since those X11 windows go along with Wayland native surfaces, it makes a lot of sense to have that X11 window manager

Why isn't Xwayland just a Wayland client?

Most Wayland compositors, Weston and WLC-based ones included, carry around a bit of XWM code, essentially a protocol extension, to deal with Xwayland. Why? What is lacking in Xwayland? Thanks, Joseph ___ wayland-devel mailing list

Re: [PATCH] compositor-drm: fix z-order inversion in plane assignment

On Tue, Sep 5, 2017 at 9:00 AM, Daniel Stone wrote: > It can't be correct to raise it to the cursor plane either, since both > cursor and overlay planes strictly stack above the scanout plane. I > guess this would read a lot easier with: > if (picked_scanout) >

[PATCH v2] libweston-desktop: add signal for title/app-id changes

As discussed on https://lists.freedesktop.org/archives/wayland-devel/2017-August/034720.html, it's useful for the shell implementation to know when these change, for example to relay the information on to taskbars or similar. To avoid ABI changes or the need to make the weston_desktop_surface