Re: [RFC] Screensaver/blanking inhibition

On 11/19/2015 05:15 AM, Jonas Ådahl wrote: On Thu, Nov 19, 2015 at 02:04:36AM -0800, Bryce Harrington wrote: On Thu, Nov 19, 2015 at 04:20:11AM -0500, Christopher Michael wrote: Just some random thoughts inlined below... On 11/19/2015 03:05 AM, Bryce Harrington wrote: A "screensaver

Re: [RFC] Screensaver/blanking inhibition

On 11/19/2015 05:28 AM, Christopher Michael wrote: On 11/19/2015 05:15 AM, Jonas Ådahl wrote: On Thu, Nov 19, 2015 at 02:04:36AM -0800, Bryce Harrington wrote: On Thu, Nov 19, 2015 at 04:20:11AM -0500, Christopher Michael wrote: Just some random thoughts inlined below... On 11/19/2015 03:05

[RFC] Screensaver/blanking inhibition

A "screensaver inhibition protocol" is on the set of needed enhancements for Wayland. This should turn off screen blanking and any running screensaver for a period, then re-enabling it later. An obvious use case is giving presentations. Other use cases include games, kiosk, automotive

Re: [RFC] Screensaver/blanking inhibition

Just some random thoughts inlined below... On 11/19/2015 03:05 AM, Bryce Harrington wrote: A "screensaver inhibition protocol" is on the set of needed enhancements for Wayland. This should turn off screen blanking and any running screensaver for a period, then re-enabling it later. An obvious

Re: [PATCH libinput 00/14] tablet: the big "tablet" -> "tablet tool" rename

Hi, On 18-11-15 05:17, Peter Hutterer wrote: The current tablet API is a bit inconsistent, we have various 'tablet' prefixes (libinput_event_tablet) and 'tool' prefixes (libinput_tool_get_serial). That made sense in the early stages when the emphasis on tools wasn't as strong as it is now.

[PATCH 0/5] Allow passing fd when adding socket for display

This patchset adds functionality to allow system-level control over handing out file descriptors for sockets, to allow tighter security when running a Wayland compositor under a Wayland session server. A Wayland session service is run with system daemon permission levels, and individual Wayland

[PATCH 3/5] socket-test: Fix indentation to follow project code style policy

From: Bryce Harrington Signed-off-by: Bryce Harrington --- tests/socket-test.c | 174 ++-- 1 file changed, 87 insertions(+), 87 deletions(-) diff --git a/tests/socket-test.c b/tests/socket-test.c

[PATCH 1/5] server: Add new api for add socket for fd

From: Sangjin Lee Currently the server can add a socket by name. To support an embedded compositor in a Simplified Mandatory Access Control Kernel (Smack) enabled environment, the embedded compositor should use the socket that it gets from the system or session compositor.

[PATCH 4/5] socket-test: Fix some comment typos

From: Bryce Harrington Signed-off-by: Bryce Harrington --- tests/socket-test.c | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/tests/socket-test.c b/tests/socket-test.c index f6db6cf..ad07f7a 100644 ---

[PATCH 2/5] wayland-server: Add code docs for new display socket API's

Signed-off-by: Bryce Harrington --- src/wayland-server.c | 67 +--- 1 file changed, 53 insertions(+), 14 deletions(-) diff --git a/src/wayland-server.c b/src/wayland-server.c index bac98bf..e84858d 100644 ---

[PATCH 5/5] socket-test: Add cases for sockets using existing fd's

From: Bryce Harrington Signed-off-by: Bryce Harrington --- tests/socket-test.c | 46 ++ 1 file changed, 46 insertions(+) diff --git a/tests/socket-test.c b/tests/socket-test.c index ad07f7a..f70c69b

Re: [RFC] Screensaver/blanking inhibition

On Thu, Nov 19, 2015 at 04:20:11AM -0500, Christopher Michael wrote: > Just some random thoughts inlined below... > > On 11/19/2015 03:05 AM, Bryce Harrington wrote: > >A "screensaver inhibition protocol" is on the set of needed enhancements > >for Wayland. This should turn off screen blanking

Re: [RFC] Screensaver/blanking inhibition

On 11/19/2015 05:04 AM, Bryce Harrington wrote: On Thu, Nov 19, 2015 at 04:20:11AM -0500, Christopher Michael wrote: Just some random thoughts inlined below... On 11/19/2015 03:05 AM, Bryce Harrington wrote: A "screensaver inhibition protocol" is on the set of needed enhancements for Wayland.

Re: [RFC] Screensaver/blanking inhibition

On Thu, Nov 19, 2015 at 02:04:36AM -0800, Bryce Harrington wrote: > On Thu, Nov 19, 2015 at 04:20:11AM -0500, Christopher Michael wrote: > > Just some random thoughts inlined below... > > > > On 11/19/2015 03:05 AM, Bryce Harrington wrote: > > >A "screensaver inhibition protocol" is on the set of

Re: [PATCH wayland 1/2] Makefile: use automake rule for compiling .S

On 11/18/15 at 01:07pm, Pekka Paalanen wrote: > From: Pekka Paalanen > > Automake seems to have its own rules for compiling an .o from an .S. > Essentially it does the same as our hand-crafted rule, but adds some > things like dependency file generation. > >

Re: [PATCH wayland 2/2] scanner: drop altmacro from dtddata.S

On 11/18/15 at 01:07pm, Pekka Paalanen wrote: > From: Pekka Paalanen > > Stop using .altmacro in dtddata.S, because clang does not yet implement > it. Turns out that we do not actually seem to need it, and we can modify > the syntax to work without it. > > Moving

Re: [RFC wayland 1/2] server: implement intact resources

On Mon, 23 Mar 2015 13:22:00 +0200 Giulio Camuffo wrote: > 2015-03-23 12:00 GMT+02:00 Marek Chalupa : > > Destroyed seems confusing to me too, since the resource is not really > > destroyed. What about inert or unalive ? > > Inert is ok, imho. On

Re: [PATCH wayland] protocol: Remove incorrect statement that attach must precede damage

On Thu, Nov 19, 2015 at 3:08 AM, Daniel Stone wrote: > Hi, > > On 18 November 2015 at 18:30, Bill Spitzak wrote: > > On Wed, Nov 18, 2015 at 7:44 AM, Derek Foreman > > wrote: > >> The documentation for wl_surface.commit makes it

Re: [RFC] Screensaver/blanking inhibition

On Thu, Nov 19, 2015 at 2:38 AM, Christopher Michael < cpmich...@osg.samsung.com> wrote: So, after issuing the inhibit request for a surface, the screensaver >> (and screenblanking) will be blocked until the surface is destroyed, >> disabled, or otherwise loses visibility or becomes

[PATCH wayland-web v0] rephrasing the index.html to be more acurate

Hello, I tryed to rephrase the index.html to be more acurate. I used Wayland, LibWayland and Weston as wording just because they are my favorite, but it does not match the name of repository. Note also that I'm not navite english speaker/writer, thus my vocabulary, my syntax and my grammatical

Re: [PATCH weston 10/11] simple-damage: Offset drawing co-ordinates not buffer start

It is not clear if this is changing anything other than the printf statement, but it makes sense as that is not printing anything about where the origin was moved. I think however the program was broken before. This fix has nothing to do with the transition to buffer damage and is required to

Re: [PATCH wayland] protocol: Remove incorrect statement that attach must precede damage

On 19/11/15 12:25 PM, Bill Spitzak wrote: > > > On Thu, Nov 19, 2015 at 3:08 AM, Daniel Stone > wrote: > > Hi, > > On 18 November 2015 at 18:30, Bill Spitzak > wrote: > > On Wed,

Re: [RFC] Screensaver/blanking inhibition

Hi, On 19 November 2015 at 19:05, Bill Spitzak wrote: > I feel like there is no need to tie it to a surface. In Wayland the client > is always notified of any changes to it's state, so it can update the > screensaver object to match. (destruction of the screensaver object

Re: [PATCH 3/5] socket-test: Fix indentation to follow project code style policy

On Thu, Nov 19, 2015 at 1:36 AM, Bryce Harrington wrote: > From: Bryce Harrington > > Signed-off-by: Bryce Harrington > --- > tests/socket-test.c | 174 > ++-- > 1 file

Re: [RFC] Screensaver/blanking inhibition

On Thu, Nov 19, 2015 at 05:38:34AM -0500, Christopher Michael wrote: > On 11/19/2015 05:28 AM, Christopher Michael wrote: > >On 11/19/2015 05:15 AM, Jonas Ådahl wrote: > >>On Thu, Nov 19, 2015 at 02:04:36AM -0800, Bryce Harrington wrote: > >>>On Thu, Nov 19, 2015 at 04:20:11AM -0500, Christopher

Re: [RFC] Screensaver/blanking inhibition

On Thu, Nov 19, 2015 at 11:12 AM, Daniel Stone wrote: > Hi, > > On 19 November 2015 at 19:05, Bill Spitzak wrote: > > I feel like there is no need to tie it to a surface. In Wayland the > client > > is always notified of any changes to it's state, so it

Re: [RFC] Screensaver/blanking inhibition

On Thu, Nov 19, 2015 at 11:05:58AM -0800, Bill Spitzak wrote: > On Thu, Nov 19, 2015 at 2:38 AM, Christopher Michael < > cpmich...@osg.samsung.com> wrote: > > So, after issuing the inhibit request for a surface, the screensaver > >> (and screenblanking) will be blocked until the surface is

Re: [RFC] Screensaver/blanking inhibition

On Thu, Nov 19, 2015 at 12:12:10PM -0800, Bill Spitzak wrote: > On Thu, Nov 19, 2015 at 11:12 AM, Daniel Stone wrote: > > > Hi, > > > > On 19 November 2015 at 19:05, Bill Spitzak wrote: > > > I feel like there is no need to tie it to a surface. In

Re: [PATCH 2/5] wayland-server: Add code docs for new display socket API's

I don't see any reason for the wl_display_add_socket_fd_auto and wl_display_add_socket_auto functions, as they are the same as passing NULL for the name to wl_display_add_socket_fd, right? Also (on the patch) it looks like if there is an error it destroys the wl_socket object, could this do the

Re: [RFC] Screensaver/blanking inhibition

On Thu, Nov 19, 2015 at 07:12:31PM +, Daniel Stone wrote: > Hi, > > On 19 November 2015 at 19:05, Bill Spitzak wrote: > > I feel like there is no need to tie it to a surface. In Wayland the client > > is always notified of any changes to it's state, so it can update the >

Re: [RFC] Screensaver/blanking inhibition

On 19 November 2015 at 20:12, Daniel Stone wrote: > Hi, > > On 19 November 2015 at 19:05, Bill Spitzak wrote: >> I feel like there is no need to tie it to a surface. In Wayland the client >> is always notified of any changes to it's state, so it can

Re: [PATCH weston v4 05/20] desktop-shell: Pass a flag bitmask instead of bool to activate()

On 17/11/15 04:10 AM, Jonas Ådahl wrote: > Although it currently only has one available flag, but that'll change. > > Signed-off-by: Jonas Ådahl > --- > desktop-shell/exposay.c | 9 ++--- > desktop-shell/shell.c | 34 ++ >

Re: [PATCH weston v4 01/20] input: Make pointer grab motion callbacks take an event struct

On 17/11/15 04:10 AM, Jonas Ådahl wrote: > Instead of only passing absolute pointer coordinates, effectively > loosing motion event data, pass a struct that can potentially contain > different types of motion events, currently being absolute and relative. > > A helper function to get resulting

Re: [PATCH wayland-web v0] rephrasing the index.html to be more acurate

On Thu, Nov 19, 2015 at 06:51:52PM +0100, Benoit Gschwind wrote: > Hello, > > I tryed to rephrase the index.html to be more acurate. I used Wayland, > LibWayland and Weston as wording just because they are my favorite, but it > does not match the name of repository. > > Note also that I'm not

Re: [PATCH v5 wayland] protocol: add wl_pointer.frame, axis_source, axis_stop, and axis_discrete

Hi, On 19 November 2015 at 01:21, Bill Spitzak wrote: > On Wed, Nov 18, 2015 at 2:46 PM, Peter Hutterer > wrote: >> discrete events are latching for axis events though, they're not just >> grouped in the same frame, they always precede the axis

Re: [PATCH wayland] protocol: Remove incorrect statement that attach must precede damage

Hi, On 18 November 2015 at 18:30, Bill Spitzak wrote: > On Wed, Nov 18, 2015 at 7:44 AM, Derek Foreman > wrote: >> The documentation for wl_surface.commit makes it clear that the >> application of damage follows attach during the commit, so it >>

Re: [PATCH weston v4 06/20] compositor: Keep track of what views were activated by clicking

On Thu, Nov 19, 2015 at 12:23:34PM +1000, Peter Hutterer wrote: > On Tue, Nov 17, 2015 at 06:10:52PM +0800, Jonas Ådahl wrote: > > Adds a weston_view_activate() that can be passed an additional active > > flag WESTON_ACTIVATE_CLICKED, that the shell passes when a view was > > activated by

Re: [PATCH weston v4 02/20] desktop-shell: Track the black surface by its view

On Tue, Nov 17, 2015 at 06:10:48PM +0800, Jonas Ådahl wrote: > In preparation for further refactoring. > > Signed-off-by: Jonas Ådahl > Signed-off-by: Arnaud Vrac Acked-by: Peter Hutterer Cheers, Peter > --- >

Re: [PATCH weston v4 03/20] desktop-shell: Change switcher to track views

On Tue, Nov 17, 2015 at 06:10:49PM +0800, Jonas Ådahl wrote: > Preparation for future refactorings. > > Signed-off-by: Jonas Ådahl Acked-by: Peter Hutterer Cheers, Peter > --- > desktop-shell/shell.c | 22 +++--- > 1 file

Re: [PATCH weston v4 01/20] input: Make pointer grab motion callbacks take an event struct

On Thu, Nov 19, 2015 at 12:23:00PM +1000, Peter Hutterer wrote: > On Tue, Nov 17, 2015 at 06:10:47PM +0800, Jonas Ådahl wrote: > > Instead of only passing absolute pointer coordinates, effectively > > loosing motion event data, pass a struct that can potentially contain > > different types of

Re: [PATCH weston v4 14/20] clients/resizor: Use pointer locking for resizing window

On Tue, Nov 17, 2015 at 06:11:00PM +0800, Jonas Ådahl wrote: > Resizes the window using pointer locking when holding the left pointer > button down. The pointer lock cursor position hint is used to warp the > pointer to the same position relative to the bottom right corner. > > Signed-off-by:

Re: black surface in desktop shell fullscreen mode

Hi Pekka How to not use the black surface behind the fullscreen surface? I want to have a try for the special needs to switch the apps. I can't use the minimize because it can't restore to its original shape. Thank you. Best Regards Nancy 2015-10-13 18:31 GMT+08:00 Pekka Paalanen

Re: [PATCH weston v4 20/20] clients/clickdot: Toggle maximized state with 'm'

On Tue, Nov 17, 2015 at 06:11:06PM +0800, Jonas Ådahl wrote: > In order to test wapring when pointer confinemen region changes, add typo, "warping" Cheers, Peter > key binding to the maximized state without using the mouse. > > Signed-off-by: Jonas Ådahl > Reviewed-by:

Re: [PATCH weston v4 17/20] clients/clickdot: Reset motion lines on Backspace

On Tue, Nov 17, 2015 at 06:11:03PM +0800, Jonas Ådahl wrote: > Clear the white lines that is drawn by pointer motions. It makes it > easier to debug pointer movements as one won't need to restart clickdot > just to get a clean plate. > > Signed-off-by: Jonas Ådahl > --- >

Re: [PATCH weston v4 18/20] window: Add API for manually set confine region

On Tue, Nov 17, 2015 at 06:11:04PM +0800, Jonas Ådahl wrote: > We can use this to test more complex confine regions. > > Signed-off-by: Jonas Ådahl Reviewed-by: Peter Hutterer Cheers, Peter > --- > clients/window.c | 69 >

Re: [PATCH weston v4 13/20] clients: Add API for pointer locking and pointer confinement

On Tue, Nov 17, 2015 at 06:10:59PM +0800, Jonas Ådahl wrote: > Signed-off-by: Jonas Ådahl > Reviewed-by: Bryce Harrington > --- > > Changes since v3: > > Uses the XML file from wayland-protocols. > > Updated implementation given interface renaming. >

Re: [PATCH] Refine compositor grabs behavior

On Thu, Nov 12, 2015 at 01:27:05PM +0100, Carlos Garnacho wrote: > Hey there, > > I think it is worth to bring back some discussion on the client-side > behavior during compositor grabs which I started a few months ago, for > reference the thread started at: >

Re: [PATCH weston v4 05/20] desktop-shell: Pass a flag bitmask instead of bool to activate()

On Thu, Nov 19, 2015 at 05:04:48PM -0600, Derek Foreman wrote: > On 17/11/15 04:10 AM, Jonas Ådahl wrote: > > Although it currently only has one available flag, but that'll change. > > > > Signed-off-by: Jonas Ådahl > > --- > > desktop-shell/exposay.c | 9 ++--- > >

Re: [PATCH weston v4 04/20] desktop-shell: Make activate() take a view instead of surface

On Tue, Nov 17, 2015 at 06:10:50PM +0800, Jonas Ådahl wrote: > In preparation for further refactorings. > > Signed-off-by: Jonas Ådahl Acked-by: Peter Hutterer Cheers, Peter > --- > desktop-shell/exposay.c | 6 +++--- > desktop-shell/shell.c

Re: [PATCH weston v4 15/20] clients/clickdot: Use pointer confinement to confine drawed line

On Tue, Nov 17, 2015 at 06:11:01PM +0800, Jonas Ådahl wrote: > Use pointer confinement to make the line drawing not go outside the > drawing area. It is toggled with the right pointer button. > > Signed-off-by: Jonas Ådahl patch itself is Reviewed-by: Peter Hutterer

Re: [PATCH wayland-protocols 1/2] Introduce wp_relative_pointer interface

On Thu, Nov 19, 2015 at 10:09:48AM +1000, Peter Hutterer wrote: > On Tue, Nov 17, 2015 at 06:09:17PM +0800, Jonas Ådahl wrote: > > The wp_relative_pointer interface is an extension to the wl_pointer > > interface created from wl_seat. It has the same focus, but adds the > > functionality of

Touch event delayed or missing with weston 1.8.0 and qtwayland 5.4.2

Dear Community, I am using following components and seeing sometime touch doesn't respond (seems touch_up event delayed or some touch event missing). For example back button on screen takes time to go back to desired screen or I need to touch it again. linux 3.14.28 weston 1.8.0 with ivi-shell

Re: [PATCH wayland v2] protocol: Add wl_surface.damage_buffer

On 18/11/15 09:37 PM, Christopher Michael wrote: > I am certainly not against these changes .. +1 for the effort ;) > > However, I would like to know (and possible others would also), what > does this mean for toolkits ?? Aside from bumping compositor and surface > versions, what sort of changes

Re: [PATCH weston 08/11] compositor: ignore surface_damage with negative height or width

On 18/11/15 07:33 PM, Bill Spitzak wrote: > > > On Wed, Nov 18, 2015 at 2:32 PM, Derek Foreman > wrote: > > If we pass negative height or width on to pixman we get error messages > in the log. > > Signed-off-by: Derek Foreman

Re: [PATCH weston v2 0/9] weston wayland-protocols migration

On Tue, 17 Nov 2015 16:00:26 +0800 Jonas Ådahl wrote: > Hi again, > > This is the second version of the weston wayland-protocols migration > patch series. > > Overall, it's pretty much the same, but here are the differences: > > Naming is updated to new naming (wl -> wp, N

Re: [PATCH weston 11/11] simple-damage: Add --use-buffer-damage flag

On 18/11/15 07:24 PM, Bill Spitzak wrote: > As this code is going to be referred to by people trying to figure out > wayland, it might be best to use this by default. Fall back to the old > damage request only if the api is too old or if a special switch is passed. I agree, but I'll wait for

Re: [PATCH weston 10/11] simple-damage: Offset drawing co-ordinates not buffer start

On 18/11/15 07:31 PM, Bill Spitzak wrote: > You sure this has to change? If I'm posting damage in buffer co-ordinates, I need to know what buffer co-ordinates to use. Currently, the code moves the *data pointer and does its drawing as if everything is still at 0,0. ie) if we set a buffer