Process for implementing a double buffer on Wayland

Hi guys, I just need some guidance on how to implement double buffering on Shared Memory. I'm not using OpenGL I've created 2 buffers of the same size (800x600 pixels). So I want the input buffer to get filled off-screen, while the output buffer will show the content on-screen. First of

Re: Process for implementing a double buffer on Wayland

Hi Mike, On 25 November 2015 at 16:06, Mike Johnson wrote: > I've created 2 buffers of the same size (800x600 pixels). So I want the > input buffer to get filled off-screen, while the output buffer will show the > content on-screen. > > First of all what sort of content

Re: [PATCH] Introduce the authorizer protocol

Hi, On 25 November 2015 at 16:14, Pekka Paalanen wrote: > On Tue, 24 Nov 2015 18:07:34 +0100 > Mariusz Ceier wrote: > > > Hi, > > > > On 24 November 2015 at 17:35, Giulio Camuffo > > wrote: > > > > > 2015-11-24 18:16

Re: [RFC] Declare enumeration wl_output.transform as bitfield.

Hi, On 25 November 2015 at 14:17, Auke Booij wrote: > On 25 November 2015 at 13:43, Daniel Stone wrote: >> Warnings aren't harmless though; there's a reason we don't (shouldn't) >> have any in our build. Every 'oh, just ignore that' warning drowns out >>

Re: [RFC wayland-protocols v2] Introduce the restricted_registry protocol

Hi, It's missing README, but otherwise it looks good to me: Reviewed-by: Mariusz Ceier Mariusz Ceier On 25 November 2015 at 15:10, Giulio Camuffo wrote: > This new extension is used by clients wanting to execute priviledged > actions such

RE: Process for implementing a double buffer on Wayland

> Date: Wed, 25 Nov 2015 16:18:52 + > Subject: Re: Process for implementing a double buffer on Wayland > From: dan...@fooishbar.org > To: mikeyj...@hotmail.com > CC: wayland-devel@lists.freedesktop.org > > Hi Mike, > > On 25 November 2015 at 16:06, Mike Johnson

Re: [RFC wayland] Track protocol object versions inside wl_proxy.

On Wed, Nov 25, 2015 at 10:15 AM, Derek Foreman wrote: > On 13/11/15 12:21 PM, Jason Ekstrand wrote: >> On Fri, Nov 13, 2015 at 3:18 AM, Giulio Camuffo >> wrote: >>> So do i understand correctly that if the app creating the >>> wl_compositor was

Re: [RFC wayland] Track protocol object versions inside wl_proxy.

On 13/11/15 12:21 PM, Jason Ekstrand wrote: > On Fri, Nov 13, 2015 at 3:18 AM, Giulio Camuffo > wrote: >> So do i understand correctly that if the app creating the >> wl_compositor was built against a libwayland without this patch the >> version returned in mesa by

Re: [RFC wayland] Track protocol object versions inside wl_proxy.

On 25/11/15 12:25 PM, Jason Ekstrand wrote: > On Wed, Nov 25, 2015 at 10:15 AM, Derek Foreman > wrote: >> On 13/11/15 12:21 PM, Jason Ekstrand wrote: >>> On Fri, Nov 13, 2015 at 3:18 AM, Giulio Camuffo >>> wrote: So do i understand

Re: Process for implementing a double buffer on Wayland

Le 25/11/2015 17:18, Daniel Stone a écrit : > Hi Mike, > > On 25 November 2015 at 16:06, Mike Johnson wrote: >> I've created 2 buffers of the same size (800x600 pixels). So I want the >> input buffer to get filled off-screen, while the output buffer will show the >>

Re: [RFC wayland] Track protocol object versions inside wl_proxy.

On 13/11/15 12:21 PM, Jason Ekstrand wrote: > On Fri, Nov 13, 2015 at 3:18 AM, Giulio Camuffo > wrote: >> So do i understand correctly that if the app creating the >> wl_compositor was built against a libwayland without this patch the >> version returned in mesa by

Re: [RFC] Declare enumeration wl_output.transform as bitfield.

On Wed, Nov 25, 2015 at 03:25:55PM +, Daniel Stone wrote: > Hi, > > On 25 November 2015 at 14:17, Auke Booij wrote: > > On 25 November 2015 at 13:43, Daniel Stone wrote: > >> Warnings aren't harmless though; there's a reason we don't (shouldn't) > >>

Re: [RFC wayland] Track protocol object versions inside wl_proxy.

On Nov 25, 2015 12:03 PM, "Derek Foreman" wrote: > > On 13/11/15 12:21 PM, Jason Ekstrand wrote: > > On Fri, Nov 13, 2015 at 3:18 AM, Giulio Camuffo wrote: > >> So do i understand correctly that if the app creating the > >> wl_compositor was built

Re: [PATCH] Introduce the authorizer protocol

On Tue, 24 Nov 2015 18:07:34 +0100 Mariusz Ceier wrote: > Hi, > > On 24 November 2015 at 17:35, Giulio Camuffo > wrote: > > > 2015-11-24 18:16 GMT+02:00 Mariusz Ceier : > > > Hi, > > > How the clients will know:

Re: black surface in desktop shell fullscreen mode

Hi Pekka I have another question about the fullscreen NULL buffer display black surface. Why the fullscreen App call hide(commit Null buffer), then start another App, only the fullscreen App can show normally? Is the normal screen App's layer below on the black surface? Best Regards Nancy

check layer orders

Dear all: Is there any command to print the desktop shell layer orders? Thank you. Best Regards Nancy ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel

Re: [RFC wayland-protocols v2] Add screensaver inhibition protocol

On 25 November 2015 at 08:24, Bryce Harrington wrote: > On Wed, Nov 25, 2015 at 08:09:16AM +0100, Michal Suchanek wrote: >> Hello >> >> On 25 November 2015 at 07:49, Bryce Harrington wrote: >> > This interface allows disabling of

[RFC] Declare enumeration wl_output.transform as bitfield.

The definition of a bitfield is that each bit has a distinct meaning, which is the case for the enumeration wl_output.transform: - bit 0: rotate by 90 degree - bit 1: rotate by 180 degree - bit 2: flip around vertical axis Every other value can be constructed by ORing together the above bits: -

Re: Changing wl_output.transform type to unsigned?

Hi, On Tue, Nov 24, 2015 at 2:48 PM, Auke Booij wrote: > On 24 November 2015 at 12:41, Nils Chr. Brause > wrote: >> On Mon, Nov 16, 2015 at 11:46 AM, Pekka Paalanen wrote: >>> On Sun, 15 Nov 2015 22:17:38 +0100 >>> "Nils Chr.

Re: [PATCH] Introduce the authorizer protocol

2015-11-24 20:53 GMT+02:00 Derek Foreman : > On 24/11/15 09:16 AM, Giulio Camuffo wrote: >> This new extension is used by clients wanting to execute priviledged >> actions such as taking a screenshot. >> The usual way of granting special priviledged to apps is to fork and

Re: [RFC] Declare enumeration wl_output.transform as bitfield.

Hi, On 25 November 2015 at 12:08, Nils Christopher Brause wrote: > 3. The API change is negligible. Every request that accepts this bitfield >expects a number in the range of zero to seven. These numbers can be >represented in and converted between signed and

Re: [RFC] Declare enumeration wl_output.transform as bitfield.

On 25 November 2015 at 13:43, Daniel Stone wrote: > Hi, > > On 25 November 2015 at 12:08, Nils Christopher Brause > wrote: >> 3. The API change is negligible. Every request that accepts this bitfield >>expects a number in the range of zero to

Re: [PATCH libinput v9 0/2] add orientation, size and pressure of touch

Hi, On Tue, Nov 24, 2015 at 1:41 AM, Peter Hutterer wrote: > On Mon, Nov 23, 2015 at 07:58:28PM +0100, Andreas Pokorny wrote: > [...] > > measured values on the e4.5 jumped a lot further. I need a more accurate > > method for that. In the second round I will probably

[PATCH weston 3/4] ivi-shell: fix layout_layer.view_list is not initilized per a screen.

From: Nobuhiko Tanibata This is potential bug when it supports several screens. If view_list is initilized here, the views, which are set by the previous screen, are cleared. So View list shall be initilized in front of wl_list_for_each of all screens.

[RFC wayland-protocols v2] Introduce the restricted_registry protocol

This new extension is used by clients wanting to execute priviledged actions such as taking a screenshot. The usual way of granting special priviledged to apps is to fork and exec them in the compositor, and then checking if the client is the known one when it binds the restricted global

[PATCH weston 0/4] fix bugs and TODO to support multi screens

Hi, I am proposing 4 patches to fix potential bugs and TODOs to support multi screens. Best Regards, Tanibata ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel

[PATCH weston 1/4] ivi-shell: fix TODO which expects only one screen in the system.

From: Nobuhiko Tanibata It just return the first screen found in screen list. Signed-off-by: Nobuhiko Tanibata Reviewed-by: Pekka Paalanen --- ivi-shell/ivi-layout.c | 5 ++--- 1 file

[PATCH weston 2/4] ivi-shell: avoid inserting a ivi_layer to multiple screens.

From: Nobuhiko Tanibata In just previous wl_list_for_each_safe, list of layer in a screen is cleaned up. And then, the list is re-constructed from pending.layer_list. In this re-construction, if order.link of a layer were inserted into a screen whose number

[PATCH weston 4/4] ivi-shell: remove a code which expects only a screen in the system.

From: Nobuhiko Tanibata It breaks from wl_list_for_each of screens when the frist screen found. Signed-off-by: Nobuhiko Tanibata Reviewed-by: Pekka Paalanen --- ivi-shell/ivi-layout.c | 2