Re: [PATCH wayland-protocols] xdg-shell: Introduce xdg_toplevel capabilities

On Wed, Jul 20, 2016 at 11:12:03AM +0200, Quentin Glidic wrote: > On 15/07/2016 13:00, Jonas Ådahl wrote: > > The xdg_toplevel capabilities are meant to let the compositor know what > > configurations a client can be configured to. This is meant to make it > > possible to disallow a compositor to m

Re: [PATCH wayland-protocols] Introduce xdg-foreign protocol

On Wed, Jul 20, 2016 at 12:04:04PM -0700, Yong Bakos wrote: > Hi Jonas, > > > On Jul 13, 2016, at 12:58 AM, Jonas Ådahl wrote: > > > > xdg-foreign is a protocol meant to enable setting up inter surface > > relationships across clients. Potential use cases are out-of-process > > dialogs, such as

[PATCH libinput 11/14] evdev: switch three ints to booleans

And a minor rename to make it more obvious Signed-off-by: Peter Hutterer --- src/evdev-mt-touchpad-buttons.c | 2 +- src/evdev-mt-touchpad.c | 6 +++--- src/evdev.c | 17 + src/evdev.h | 6 +++--- 4 files changed, 16 insertions(+

[PATCH libinput 03/14] evdev: split out slot init

Signed-off-by: Peter Hutterer --- src/evdev.c | 131 +--- 1 file changed, 73 insertions(+), 58 deletions(-) diff --git a/src/evdev.c b/src/evdev.c index b0f2870..0687de0 100644 --- a/src/evdev.c +++ b/src/evdev.c @@ -1392,6 +1392,77 @@ evde

[PATCH libinput 09/14] evdev: split evdev_dispatch and fallback_dispatch into separate entities

Signed-off-by: Peter Hutterer --- src/evdev-tablet.c | 2 +- src/evdev-tablet.h | 2 ++ src/evdev.c| 81 +- src/evdev.h| 17 4 files changed, 58 insertions(+), 44 deletions(-) diff --git a/src/evdev-tablet.c b/src

[PATCH libinput 06/14] evdev: move the relative deltas for normal devices to the fallback dispatch

Signed-off-by: Peter Hutterer --- src/evdev.c | 36 ++-- src/evdev.h | 4 ++-- 2 files changed, 24 insertions(+), 16 deletions(-) diff --git a/src/evdev.c b/src/evdev.c index 140fa73..e68eab4 100644 --- a/src/evdev.c +++ b/src/evdev.c @@ -372,10 +372,10 @@ evdev_

[PATCH libinput 08/14] evdev: move the keyboard mask into the fallback dispatch

Signed-off-by: Peter Hutterer --- src/evdev.c | 45 +++-- src/evdev.h | 13 - 2 files changed, 31 insertions(+), 27 deletions(-) diff --git a/src/evdev.c b/src/evdev.c index 620c6b7..5d6b2a9 100644 --- a/src/evdev.c +++ b/src/evdev.c @@ -92,15

[PATCH libinput 13/14] evdev: pass the dispatch interface around

The only places we should typecast from device->dispatch is where we have external entry points. Everywhere else keep the pointer to the dispatch interface we already have anyway. This way we avoid papering over a potential re-use of a function from non-evdev code, passing in the wrong dispatch.

[PATCH libinput 10/14] evdev: reshuffle the evdev_device struct fields

Have the ungrouped items at the top of the struct for better visibility. Signed-off-by: Peter Hutterer --- src/evdev.h | 24 ++-- 1 file changed, 10 insertions(+), 14 deletions(-) diff --git a/src/evdev.h b/src/evdev.h index f592032..7bc09d2 100644 --- a/src/evdev.h +++ b/sr

[PATCH libinput 14/14] evdev: rename all fallback-specific functions to a fallback_ prefix

Signed-off-by: Peter Hutterer --- src/evdev.c | 132 ++-- 1 file changed, 66 insertions(+), 66 deletions(-) diff --git a/src/evdev.c b/src/evdev.c index 6dc8302..a4dd74c 100644 --- a/src/evdev.c +++ b/src/evdev.c @@ -132,11 +132,11 @@ updat

[PATCH libinput 12/14] evdev: move the abs point into the fallback dispatch

Signed-off-by: Peter Hutterer --- src/evdev.c | 34 ++ src/evdev.h | 8 +--- 2 files changed, 27 insertions(+), 15 deletions(-) diff --git a/src/evdev.c b/src/evdev.c index 44b0be5..74693f1 100644 --- a/src/evdev.c +++ b/src/evdev.c @@ -504,7 +504,7 @@ evdev_

[PATCH libinput 07/14] evdev: move pending_event to the evdev_dispatch struct

Signed-off-by: Peter Hutterer --- src/evdev.c | 52 +--- src/evdev.h | 3 ++- 2 files changed, 31 insertions(+), 24 deletions(-) diff --git a/src/evdev.c b/src/evdev.c index e68eab4..620c6b7 100644 --- a/src/evdev.c +++ b/src/evdev.c @@ -405,7 +40

[PATCH libinput 04/14] evdev: move axis dimension handling into a single helper function

Signed-off-by: Peter Hutterer --- src/evdev.c | 42 ++ 1 file changed, 22 insertions(+), 20 deletions(-) diff --git a/src/evdev.c b/src/evdev.c index 0687de0..a7b77c8 100644 --- a/src/evdev.c +++ b/src/evdev.c @@ -2116,14 +2116,30 @@ evdev_reject_device(st

[PATCH libinput 02/14] evdev: return the dispatch method from evdev_configure_device

Rather than setting a magic device field and returning true/false just return the dispatch method. Signed-off-by: Peter Hutterer --- src/evdev.c | 43 +++ 1 file changed, 19 insertions(+), 24 deletions(-) diff --git a/src/evdev.c b/src/evdev.c index 1f77b

[PATCH libinput 05/14] evdev: move the mt struct into the evdev dispatch struct

This is only used by the fallback dispatch method, not by any of the others. Anything dispatch-specific should go into that struct. Signed-off-by: Peter Hutterer --- src/evdev.c | 74 ++--- src/evdev.h | 15 +++-- 2 files changed, 4

[PATCH libinput 00/14] evdev dispatch cleanup

This patchset cleans up the split between the device-specific dispatch and the generic evdev_device struct. Before anything that would go into the fallback dispatch (mouse, keyboards, ...) was stored in the evdev_device. This led to some duplication, e.g. the 'mt' struct wasn't used for touchpads

[PATCH libinput 01/14] evdev: move the fallback dispatch creation to evdev_configure_device

All the other devices are created in there too, unify that approach. Signed-off-by: Peter Hutterer --- src/evdev.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/evdev.c b/src/evdev.c index aeb21eb..1f77bc0 100644 --- a/src/evdev.c +++ b/src/evdev.c @@ -2290,6 +2290

[PATCH v2 libinput] udev: check wacom devices for a paired product id

The newer Wacom Cintiqs have touch devices with a different PID than the pen device. Use the new libwacom_get_paired_device call where available to pair the two devices and give them the same device group. This isn't that important just yet, so no need to force users to update to a new libwacom ve

Re: Weston on framebuffer?

On Wed, 20 Jul 2016 21:49:57 +0200 Christer Weinigel said: > Hi, > > On 07/20/2016 01:04 AM, Carsten Haitzler (The Rasterman) wrote: > >> With this I managed to get a desktop and was unable to start > >> wayland-terminal. Redrawing of the graphics felt fairly snappy, but the > >> lag from press

Re: Weston on framebuffer?

Hi, On 07/20/2016 01:04 AM, Carsten Haitzler (The Rasterman) wrote: With this I managed to get a desktop and was unable to start wayland-terminal. Redrawing of the graphics felt fairly snappy, but the lag from pressing a key on the keyboard until a character showed up in the terminal was slow,

Re: [PATCH wayland-protocols] Introduce xdg-foreign protocol

Hi Jonas, > On Jul 13, 2016, at 12:58 AM, Jonas Ådahl wrote: > > xdg-foreign is a protocol meant to enable setting up inter surface > relationships across clients. Potential use cases are out-of-process > dialogs, such as file dialogs, meant to be used by sandboxed processes > that may not have

Re: [PATCH wayland-protocols 2/3] xdg-shell: Clarify focus semantics for popup grabs

Hi Jonas, > On Jul 15, 2016, at 2:37 AM, Jonas Ådahl wrote: > > Make it clearer what the focus semantics are during a popup grab. In > short, when a grabbing popup is mapped, the top most popup will always > have keyboard focus, while pointer and touch focus works just as normal > except that on

Re: [PATCH wayland-protocols] xdg-shell: Introduce xdg_toplevel capabilities

> On Jul 15, 2016, at 4:00 AM, Jonas Ådahl wrote: > > The xdg_toplevel capabilities are meant to let the compositor know what > configurations a client can be configured to. This is meant to make it > possible to disallow a compositor to maximize, fullscreen etc a > surface, which would otherwise

Re: [PATCH wayland-protocols v4 7/7] xdg-shell: Introduce xdg_positioner

Jonas, My R'b for 1-6 of v4 stand. I think I finally grok xdg_positioner, and this seems straightforward. I would like to understand Bill's 'list of rectangles' approach, mentioned off-list, but from what I can tell it doesn't jive with current best practices. I mention this because I'm always ope

Re: [Question] About muti-thread with wayland/weston

Hi Lingyun, On 8 July 2016 at 06:52, Zhu, Lingyun wrote: > I’m trying to develop an application under Yocto, which may have multiple > (maybe 16) threads contained in one process. > > Each thread wants to have an individual connection with Weston and render > its own picture independently at the

[Question] About muti-thread with wayland/weston

Hi, guys I'm trying to develop an application under Yocto, which may have multiple (maybe 16) threads contained in one process. Each thread wants to have an individual connection with Weston and render its own picture independently at the same time. But I'm not sure whether it's feasible with We

Re: Create cross wayland-scanner for toolchain or cross-development environment

Hi Quentin. I see. My suggestion related to simplify the build process on developer machines which doesn't have pre-installed native Wayland package. And also I think it would be good if wailand-scanner output will be generated by scanner which has the same version as target machine scanner. Curr

Re: Create cross wayland-scanner for toolchain or cross-development environment

Of course, not an old lib with a never scanner! only the same. On Fri, Jul 8, 2016 at 12:24 PM, Quentin Glidic < sardemff7+wayl...@sardemff7.net> wrote: > On 08/07/2016 10:46, Andrew Kosteltsev wrote: > >> Hi Quentin. >> >> I see. My suggestion related to simplify the build process on developer >

Re: Create cross wayland-scanner for toolchain or cross-development environment

Hi Emil, Unfortunattely Mesa-11.2.2 still requires wayland-scanner. But I will check it again. Best Regards, Andrey K. 8 июля 2016 г. 13:29 пользователь "Emil Velikov" написал: Hi all, Jumping the gun a bit, hope you'll forgive me :-) On 8 July 2016 at 09:17, Quentin Glidic wrote: > On 18/05

Re: When to use libweston plugin registry

On 20.07.2016 09:45, Pekka Paalanen wrote: > Hi Armin, > > I didn't manage to catch you online, so here is re: > https://paste.debian.net/hidden/ac601ed5/ > Hi Pekka, Sorry for not being available in the past few days. I will be once again available full time starting tomorrow afternoon. > Yes

Re: [PATCH libinput] udev: check wacom devices for a paired product id

On 20/07/2016 12:02, Peter Hutterer wrote: The newer Wacom Cintiqs have touch devices with a different PID than the pen device. Use the new libwacom_get_paired_device call where available to pair the two devices and give them the same device group. This isn't that important just yet, so no need

[PATCH libinput] udev: check wacom devices for a paired product id

The newer Wacom Cintiqs have touch devices with a different PID than the pen device. Use the new libwacom_get_paired_device call where available to pair the two devices and give them the same device group. This isn't that important just yet, so no need to force users to update to a new libwacom ve

[PATCH libinput] udev: don't overwrite a previously set device group

In some cases a device may need a device group assigned by a custom udev rule or hwdb entry. Don't overwrite that with our generated one. Signed-off-by: Peter Hutterer --- udev/80-libinput-device-groups.rules.in | 1 + 1 file changed, 1 insertion(+) diff --git a/udev/80-libinput-device-groups.r

Re: [PATCH wayland-protocols] xdg-shell: Introduce xdg_toplevel capabilities

On 15/07/2016 13:00, Jonas Ådahl wrote: The xdg_toplevel capabilities are meant to let the compositor know what configurations a client can be configured to. This is meant to make it possible to disallow a compositor to maximize, fullscreen etc a surface, which would otherwise mandate the client

Re: [PATCH wayland-protocols 3/3] xdg-shell: Add resize_x/y constrain adjustment to positioner

On 15/07/2016 11:37, Jonas Ådahl wrote: In order to get feedback of available space where a client can create its popup, let it create requset that its popup rectangle being resized would it not fit the within the work area. This adds two new constrain adjustment values to the adjustment enum, an

Re: [PATCH wayland-protocols 1/3] xdg-shell: Don't require the client to obay configure sizes

On 15/07/2016 11:37, Jonas Ådahl wrote: Some clients cannot obay arbitrary dimensions configured via xdg_toplevel.configure. For example, a client surface could require to have a certain aspect ratio, or not even be able to resize at all. Prior to this patch, such clients could not be implemente

Re: [PATCH wayland-protocols v4 7/7] xdg-shell: Introduce xdg_positioner

On 24/06/2016 08:47, Jonas Ådahl wrote: xdg_positioner is a method for declarative positioning of child surfaces (currently only xdg_popup surfaces). A client creates a description of a positioning logic using the xdg_positioner interface. The xdg_positioner object is then used when creating a xd

Re: [PATCH wayland-protocols v4 6/7] xdg-shell: Make xdg_popup non-grabbing by default

On 24/06/2016 08:47, Jonas Ådahl wrote: Turn xdg_popup into plain temporary child surfaces without any grabbing or mapping order requirements by default. In order to create grabbing popup chains, a new request 'grab' is introduced which enables more or less the same semantics and requirements as

Re: [PATCH wayland-protocols v4 5/7] xdg-shell: Make get_popup take a xdg_surface instead of wl_surface

On 24/06/2016 08:47, Jonas Ådahl wrote: The reason for using wl_surface before was that xdg_popup and xdg_surface (now xdg_toplevel) had no common interface other than wl_surface, but since xdg_surface is now the base interface, lets use that. Signed-off-by: Jonas Ådahl Reviewed-by: Mike Blumen

Re: [PATCH wayland-protocols v4 4/7] xdg-shell: Improve error enum formatting some

On 24/06/2016 08:47, Jonas Ådahl wrote: The long lines stood out, break them by putting the summary on its own line. Signed-off-by: Jonas Ådahl Reviewed-by: Yong Bakos Reviewed-by: Mike Blumenkrantz Reviewed-by: Benoit Gschwind --- Trivial enough: Reviewed-by: Quentin Glidic Cheers,

Re: [PATCH wayland-protocols v4 3/7] xdg-shell: Add error codes for invalid surface state

On 24/06/2016 08:47, Jonas Ådahl wrote: Signed-off-by: Jonas Ådahl Reviewed-by: Mike Blumenkrantz Reviewed-by: Yong Bakos --- Sounds good: Acked-by: Quentin Glidic Cheers, No changes since v3. unstable/xdg-shell/xdg-shell-unstable-v6.xml | 2 ++ 1 file changed, 2 insertions(+) diff

Re: [PATCH wayland-protocols v4 2/7] xdg-shell: Put xdg_shell events after requests

On 24/06/2016 08:47, Jonas Ådahl wrote: It makes the structure consistent with most other protocols and provides a clear separation between what is done by the server and what is done by the client. Signed-off-by: Jonas Ådahl Reviewed-by: Yong Bakos Reviewed-by: Mike Blumenkrantz --- Just m

Re: [PATCH wayland-protocols v4 1/7] xdg-shell: Turn xdg_surface into a generic base interface

On 24/06/2016 08:47, Jonas Ådahl wrote: Split out toplevel window like requests and events into a new interface called xdg_toplevel, and turn xdg_surface into a generic base interface which others extends. xdg_popup is changed to extend the xdg_surface. The configure event in xdg_surface was sp

When to use libweston plugin registry

Hi Armin, I didn't manage to catch you online, so here is re: https://paste.debian.net/hidden/ac601ed5/ Yes, that's the mechanics of using the plugin registry, but I didn't think of using it for those particular entries. For libweston-core <-> backend APIs using the plugin registry seems like an

Re: [PATCH wayland-protocols] input-method: Grammar fixups

On Thu, Jun 16, 2016 at 09:16:26PM -0600, Yong Bakos wrote: > Hi Bryce, > > > On Jun 15, 2016, at 6:28 PM, Bryce Harrington wrote: > > > > From: Bryce Harrington > > > > Signed-off-by: Bryce Harrington > > --- > > unstable/input-method/input-method-unstable-v1.xml | 14 +++--- > > 1 fi

Re: [PATCH wayland-protocols v5 1/4] tablet: add v2 of the tablet protocol

All 4 patches merged, with the typo mentioned by Peter and wording change suggested by Jason, as well as with Bryce and my RBs: 2009a70..24eb670 master -> master Will let it brew over the night a and make release hopefully tomorrow. Jonas On Mon, Jul 11, 2016 at 05:13:33PM +0200, Carlos Ga

Re: [RFC PATCH wayland] wayland-server: Add API to control globals visibility

On Wed, Jul 06, 2016 at 03:45:00PM +0200, Olivier Fourdan wrote: > Add a new API to let compositor decide whether or not a wl_global > should be advertised to the clients via wl_registry_bind() or > display_get_registry() > > By using its own filter, the compositor can decide which wl_global would