Hi Daniel,
IMO, entire point of having wayland surfaces and buffers to use them for
display scanout.
If an application does not want to display its rendered content, it can use
surfaceless context or render to texture etc.
Furthermore, we don’t have information in weston about content producin
On Sat, Jul 21, 2018 at 04:31:22PM +0100, Daniel Stone wrote:
> From: Emmanuele Bassi
>
> Meson is a next generation build system, simpler than Autotools and,
> more importantly, faster and more portable. While the latter
> consideration is of lesser importance for Wayland, being easier to
> unde
On Sat, Jul 21, 2018 at 04:31:21PM +0100, Daniel Stone wrote:
> From: Emmanuele Bassi
>
> The tests that run exec-fd-leak-checker expect the binary to be located
> in the current directory. This is not always the case; for instance, the
> binaries could be built under `tests`, but be invoked unde
Any ideas?
The rest of my code can be found at:
https://github.com/adlocode/test-libweston-desktop
Regards
adlo
On Tue, 2018-07-17 at 09:21 +0100, adlo wrote:
> I am writing a compositor using libweston. I am attempting to
> implement raising windows on click. It mostly works, but it has
> int
> > > The damage region received during output repaint is in Weston's global
> > > co-ordinate space. To shift to CRTC co-ordinates, you need to
> > > translate the damage region by (-output->x, -output->y). When we are
> > > using the renderer, there is no scaling, so CRTC co-ordinates and
> > > f
Hi,
On Thu, 26 Jul 2018 at 16:11, Emil Velikov wrote:
> On 25 July 2018 at 18:36, Derek Foreman
> wrote:
> > On 2018-07-21 06:13 AM, Daniel Stone wrote:
> >> The check for the execinfo.h header is only advisory; the build will not
> >> fail if it is not present, and set HAVE_EXECINFO_H if it is
Hi Deepak,
On Wed, 25 Jul 2018 at 18:26, Deepak Singh Rawat wrote:
> > The damage region received during output repaint is in Weston's global
> > co-ordinate space. To shift to CRTC co-ordinates, you need to
> > translate the damage region by (-output->x, -output->y). When we are
> > using the re
On 25 July 2018 at 18:36, Derek Foreman wrote:
> On 2018-07-21 06:13 AM, Daniel Stone wrote:
>> The check for the execinfo.h header is only advisory; the build will not
>> fail if it is not present, and set HAVE_EXECINFO_H if it is. The check
>> was added in commit 5cfdbef3d299 ("build: Allow disa
Reviewed-by: Emre Ucan
Best regards
Emre Ucan
Engineering Software Base (ADITG/ESB)
Tel. +49 5121 49 6937
> -Original Message-
> From: wayland-devel [mailto:wayland-devel-
> boun...@lists.freedesktop.org] On Behalf Of Daniel Stone
> Sent: Freitag, 20. Juli 2018 21:07
> To: wayland-deve
Reviewed-by: Emre Ucan
Best regards
Emre Ucan
Engineering Software Base (ADITG/ESB)
Tel. +49 5121 49 6937
> -Original Message-
> From: wayland-devel [mailto:wayland-devel-
> boun...@lists.freedesktop.org] On Behalf Of Daniel Stone
> Sent: Freitag, 20. Juli 2018 21:06
> To: wayland-deve
Reviewed-by: Emre Ucan
Best regards
Emre Ucan
Engineering Software Base (ADITG/ESB)
Tel. +49 5121 49 6937
> -Original Message-
> From: wayland-devel [mailto:wayland-devel-
> boun...@lists.freedesktop.org] On Behalf Of Daniel Stone
> Sent: Freitag, 20. Juli 2018 21:06
> To: wayland-deve
Hi,
I am looking forward for this feature. Currently, I am not able to test it in
our setup.
Acked-by: Emre Ucan
Best regards
Emre Ucan
Engineering Software Base (ADITG/ESB)
Tel. +49 5121 49 6937
> -Original Message-
> From: wayland-devel [mailto:wayland-devel-
> boun...@lists.freedes
Hi Emre,
On Thu, 26 Jul 2018 at 14:54, Ucan, Emre (ADITG/ESB)
wrote:
> We are currently querying supported modifiers only from gpu drivers via
> EGL_EXT_image_dma_buf_modifiers extension.
> But we should also query and advertise modifiers which are supported by DRM
> device. We are already gett
Hi all,
We are currently querying supported modifiers only from gpu drivers via
EGL_EXT_image_dma_buf_modifiers extension.
But we should also query and advertise modifiers which are supported by DRM
device. We are already getting this information via IN_FORMATS of a drm plane.
IMO, it is not en
Hi,
On Thu, 26 Jul 2018 at 02:53, Peter Hutterer wrote:
> On Tue, Jul 24, 2018 at 03:42:50PM +1000, Peter Hutterer wrote:
> > Sending this out as patch even though what really matters is the
> > output. Which is... here, tadaaa!
> >
> > https://people.freedesktop.org/~whot/libinput-rtd/
>
> fwiw,
Hi Jasper,
On Thu, 26 Jul 2018 at 03:53, Jasper St. Pierre wrote:
> From IRC conversations with krh a long time ago, this is indeed intentional
> and the cursor surface should "lose its role" in modern parlance.
>
> The original intention was to prevent glitching of the cursor surface. e.g.
> I
16 matches
Mail list logo