Re: [PATCH] xdg-shell: add set_max_size request

On Mon, 04 Apr 2016 19:44:58 + "Jasper St. Pierre" said: > I think min/max hints are acceptable in xdg-shell. i agree. they are realistic things a apps have as constraints on their content. knowing in advance what those constraints might be can make life for a

Re: [PATCH weston 1/3] zunitc: fix spelling mistake (Eric Engestrom)

> Date: Sat, 2 Apr 2016 17:03:13 +0100 > From: Eric Engestrom > To: wayland-devel@lists.freedesktop.org > Cc: Eric Engestrom > Subject: [PATCH weston 1/3] zunitc: fix spelling mistake > Message-ID: <1459612995-8573-1-git-send-email-e...@engestrom.ch> > >

Re: [PATCH wayland 2/2] wayland-client: fix spelling mistake (Eric Engestrom)

> Date: Sat, 2 Apr 2016 17:04:05 +0100 > From: Eric Engestrom > To: wayland-devel@lists.freedesktop.org > Cc: Eric Engestrom > Subject: [PATCH wayland 2/2] wayland-client: fix spelling mistake > Message-ID:

Re: [PATCH wayland 1/2] protocol: fix spelling mistake (Eric Engestrom)

> Date: Sat, 2 Apr 2016 17:04:04 +0100 > From: Eric Engestrom > To: wayland-devel@lists.freedesktop.org > Cc: Eric Engestrom > Subject: [PATCH wayland 1/2] protocol: fix spelling mistake > Message-ID: <1459613045-9905-1-git-send-email-e...@engestrom.ch> >

Re: [PATCH libinput] fix spelling mistakes (Eric Engestrom)

> Date: Sun, 3 Apr 2016 01:47:43 +0100 > From: Eric Engestrom > To: wayland-devel@lists.freedesktop.org > Cc: Eric Engestrom > Subject: [PATCH libinput] fix spelling mistakes > Message-ID: <1459644463-5419-1-git-send-email-e...@engestrom.ch> > >

Re: [PATCH weston 3/3] client: fix spelling mistake (Eric Engestrom)

> Date: Sat, 2 Apr 2016 17:03:15 +0100 > From: Eric Engestrom > To: wayland-devel@lists.freedesktop.org > Cc: Eric Engestrom > Subject: [PATCH weston 3/3] client: fix spelling mistake > Message-ID: <1459612995-8573-3-git-send-email-e...@engestrom.ch> > >

Re: [PATCH weston 2/3] xwayland: fix spelling mistake (Eric Engestrom)

> Date: Sat, 2 Apr 2016 17:03:14 +0100 > From: Eric Engestrom > To: wayland-devel@lists.freedesktop.org > Cc: Eric Engestrom > Subject: [PATCH weston 2/3] xwayland: fix spelling mistake > Message-ID: <1459612995-8573-2-git-send-email-e...@engestrom.ch> > >

Re: [PATCH wayland v2 0/1] protocol: Add summaries to event parameters

> On Sat, Apr 2, 2016 at 2:48 PM, Yong Bakos wrote: > From: Yong Bakos > > This v2 patch incorporates some recent feedback per v1. Two things to note: > > 1) The 'name' parameter in wl_registry events has been changed to "numeric > name" >

Re: [PATCH] xdg-shell: add set_max_size request

I think min/max hints are acceptable in xdg-shell. On Mon, Apr 4, 2016, 12:33 PM Mike Blumenkrantz < michael.blumenkra...@gmail.com> wrote: > On Mon, Apr 4, 2016 at 3:30 PM Olivier Fourdan > wrote: > >> >> Hi Mike, >> >> - Original Message - >> > [...] >> > >> >

Re: [PATCH] xdg-shell: add set_max_size request

On Mon, Apr 4, 2016 at 3:30 PM Olivier Fourdan wrote: > > Hi Mike, > > - Original Message - > > [...] > > > > Yes, I know you are not currently advocating for it, but you've proved my > > point--others will see this go in and then they will push for it. Adding > >

Re: [PATCH] xdg-shell: add set_max_size request

Hi Mike, - Original Message - > [...] > > Yes, I know you are not currently advocating for it, but you've proved my > point--others will see this go in and then they will push for it. Adding > any form of size hints is a slipper slope which leads to more size hints > imo. My turn to

Re: [PATCH wayland-protocols] unstable: Add the Wayland Wobbly Windows protocol

On 01/04/16 11:19 AM, Daniel Stone wrote: > Hi, > > On 1 April 2016 at 16:14, Derek Foreman wrote: >> diff --git a/unstable/www/www-unstable-v1.xml >> b/unstable/www/www-unstable-v1.xml >> new file mode 100644 >> index 000..cb928a9 >> --- /dev/null >> +++

Re: [PATCH] xdg-shell: add set_max_size request

On Mon, Apr 4, 2016 at 1:17 PM Olivier Fourdan wrote: > Hi Mike, > > > Hm, you raise some interesting points. However, I think your argument is > > somewhat misled by your claim that "this case is unique". If there is an > > application which does not want to be larger than

[PATCH weston 2/3] xwayland: fix spelling mistake

Signed-off-by: Eric Engestrom --- xwayland/selection.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xwayland/selection.c b/xwayland/selection.c index 6f5328d..bd5e28a 100644 --- a/xwayland/selection.c +++ b/xwayland/selection.c @@ -117,7 +117,7 @@

[PATCH wayland 2/2] wayland-client: fix spelling mistake

Signed-off-by: Eric Engestrom --- src/wayland-client.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/wayland-client.c b/src/wayland-client.c index 297c7a5..33033e7 100644 --- a/src/wayland-client.c +++ b/src/wayland-client.c @@ -1587,7 +1587,7 @@

Re: history/semantics of uint32_t name

The word "name" strongly implies that the data is a string. It does not help that right next to it is "interface" which *is* a string. Some variation of "server's id" would be clearer. On Fri, Apr 1, 2016 at 12:59 AM, Pekka Paalanen wrote: > On Fri, 1 Apr 2016 09:44:07

[PATCH weston 3/3] client: fix spelling mistake

Signed-off-by: Eric Engestrom --- clients/flower.c | 2 +- clients/scaler.c | 2 +- clients/smoke.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/clients/flower.c b/clients/flower.c index aafc63c..34287fd 100644 --- a/clients/flower.c +++

[PATCH libinput] fix spelling mistakes

Signed-off-by: Eric Engestrom --- doc/t440-support.dox | 2 +- src/evdev-tablet.c | 2 +- src/evdev.c | 2 +- src/filter.c | 2 +- src/libinput.h | 8 5 files changed, 8 insertions(+), 8 deletions(-) diff --git a/doc/t440-support.dox

[PATCH weston 1/3] zunitc: fix spelling mistake

Signed-off-by: Eric Engestrom --- tools/zunitc/inc/zunitc/zunitc.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/zunitc/inc/zunitc/zunitc.h b/tools/zunitc/inc/zunitc/zunitc.h index 0fa78e3..6ac6f39 100644 --- a/tools/zunitc/inc/zunitc/zunitc.h +++

[PATCH weston] zunitc: remove `break` after `return`

Signed-off-by: Eric Engestrom --- tools/zunitc/src/zuc_base_logger.c | 6 -- tools/zunitc/src/zunitc_impl.c | 11 --- 2 files changed, 17 deletions(-) diff --git a/tools/zunitc/src/zuc_base_logger.c b/tools/zunitc/src/zuc_base_logger.c index 1beb60d..cdbd9ea

Re: [PATCH] xdg-shell: add set_max_size request

Hi Mike, > Hm, you raise some interesting points. However, I think your argument is > somewhat misled by your claim that "this case is unique". If there is an > application which does not want to be larger than a certain size, why could > there not also be an application which does not want to be

Re: [PATCH] xdg-shell: add set_max_size request

Hm, you raise some interesting points. However, I think your argument is somewhat misled by your claim that "this case is unique". If there is an application which does not want to be larger than a certain size, why could there not also be an application which does not want to be smaller than a

Re: [PATCH] xdg-shell: add set_max_size request

Hi Mike, Thanks for starting the discussion! :) - Original Message - > Just to play devil's advocate, do we really want to start getting into size > hint type stuff? After this will be min size, then step size, then aspect, > ... I think these are different issues. min size, step size,

Re: Introduction and updates from NVIDIA

Hi Miguel, On 2 April 2016 at 11:12, Miguel Angel Vico wrote: > On Fri, 1 Apr 2016 17:28:17 -0700 > Andy Ritger wrote: >> > (As an aside, I wonder if it's properly done in FIFO mode as well; >> > the compositor may very validly choose not to dequeue a

Re: Introduction and updates from NVIDIA

Hi, On 2 April 2016 at 01:28, Andy Ritger wrote: > On Tue, Mar 29, 2016 at 05:44:41PM +0100, Daniel Stone wrote: >> On 23 March 2016 at 00:12, Andy Ritger wrote: >> > Also, mailbox mode versus FIFO mode should essentially equate to Vsync >> > off versus

Re: [PATCH] xdg-shell: add set_max_size request

Just to play devil's advocate, do we really want to start getting into size hint type stuff? After this will be min size, then step size, then aspect, ... On Mon, Apr 4, 2016 at 5:14 AM Olivier Fourdan wrote: > Some application may wish to restrict their window in size, but

Re: [PATCH] protocol: Extend wl_touch with touch point shape

Hi, On 3 April 2016 at 23:35, Peter Hutterer wrote: > Agreed. And please specify the exact details of what is considered the > major/minor axis (direction, orientation) and where the logical 0 is for the > orientation. Referencing the kernel isn't good enough here, we

Re: [PATCH libinput] touchpad: add a middle button software area

Hi, On 04-04-16 03:40, Peter Hutterer wrote: Middle button interaction is most commonly to paste and it is a single-event interaction (button press). We provided middle button in software button mode by emulating it with a two-finger press with L+R down at the same time. This is also what many

[PATCH] xdg-shell: add set_max_size request

Some application may wish to restrict their window in size, but xdg-shell has no mecanism for the client to advertise such a maximimum size. As a result, the compositor may try to maximize or fullscreen a window while the client would not allow for the requested size. Add a new request

[PATCH weston v2 7/7] ivi-shell: rework configure_surface notification

The add_notification_configure_surface API accepts a simple wl_listener instead of a ivi-shell specific notification function. Therefore, the API is renamed to add_listener_configure_surface. This change has several advantages: 1. Code cleanup 2. No dynamic memory allocation. Listeners are

[PATCH weston v2 6/7] ivi-shell: rework remove_surface notification

The add_notification_remove_surface API accepts a simple wl_listener instead of a ivi-shell specific notification function. Therefore, the API is renamed to add_listener_remove_surface. This change has several advantages: 1. Code cleanup 2. No dynamic memory allocation. Listeners are allocated

[PATCH weston v2 1/7] ivi-shell: rework surface_add_notification API

The surface_add_notification API accepts a simple wl_listener instead of a ivi-shell specific notification function. Therefore, the API is renamed to surface_add_listener. This change has several advantages: 1. Code cleanup 2. No dynamic memory allocation. Listeners are allocated by controller

[PATCH weston v2 2/7] ivi-shell: rework layer_add_notification API

The layer_add_notification API accepts a simple wl_listener instead of a ivi-shell specific notification function. Therefore, the API is renamed to layer_add_listener. This change has several advantages: 1. Code cleanup 2. No dynamic memory allocation. Listeners are allocated by controller

[PATCH weston v2 5/7] ivi-shell: rework remove_layer notification

The add_notification_remove_layer API accepts a simple wl_listener instead of a ivi-shell specific notification function. Therefore, the API is renamed to add_listener_remove_layer. This change has several advantages: 1. Code cleanup 2. No dynamic memory allocation. Listeners are allocated by

[PATCH weston v2 0/7] IVI Layout Notification APIs Rework

v2 Changes: - add description to add_listener* APIs. - squash rework and remove patches into one. - don't cast void pointers unnecessarily. - don't remove comma in the end of ivi_layout_interface struct. Emre Ucan (7): ivi-shell: rework surface_add_notification API ivi-shell: rework

[PATCH weston v2 4/7] ivi-shell: rework create_layer_notification

The add_notification_layer_surface API accepts a simple wl_listener instead of a ivi-shell specific notification function. Therefore, the API is renamed to add_listener_layer_surface. This change has several advantages: 1. Code cleanup 2. No dynamic memory allocation. Listeners are allocated

[PATCH weston v2 3/7] ivi-shell: rework create_surface notification

The add_notification_create_surface API accepts a simple wl_listener instead of a ivi-shell specific notification function. Therefore, the API is renamed to add_listener_create_surface. This change has several advantages: 1. Code cleanup 2. No dynamic memory allocation. Listeners are allocated