Hi Pekka,
Thanks for your reply. Yes, preferably if I can hide the map and unmap from
client, in this case I cannot because it is part of a desktop shell. After
I unmap it and remap the view next time, it is not expected the shell to
continue from last draw. I would want the shell be drawing total
Hi Adam,
On Fri, 3 Aug 2018 at 19:05, Adam Jackson wrote:
> On Thu, 2018-08-02 at 17:21 -0700, Madhurkiran Harikrishnan wrote:
> > The original implementation always chose first egl config for pbuffer
> > surface type, however the returned configs are implementation specific
> > and egl config ma
On Thu, 2018-08-02 at 17:21 -0700, Madhurkiran Harikrishnan wrote:
> The original implementation always chose first egl config for pbuffer
> surface type, however the returned configs are implementation specific
> and egl config may not always match between ctx and surface. Hence,
> use gr->egl_con
On August 3, 2018 6:12 PM, Dorota Czaplejewicz
wrote:
> Provides the ability to emulate keyboards by applications. Complementary to
> input-method protocol.
>
> The interface is a mirror copy of wl_keyboard, with removed serials, and
> added seat binding.
> ---
> Hello,
>
> this is the change I
Provides the ability to emulate keyboards by applications. Complementary to
input-method protocol.
The interface is a mirror copy of wl_keyboard, with removed serials, and added
seat binding.
---
Hello,
this is the change I wanted to send previously (sorry).
Regards,
Dorota Czaplejewicz
Make
Provides the ability to emulate keyboards by applications. Complementary to
input-method protocol.
The interface is a mirror copy of wl_keyboard, with removed serials, and added
seat binding.
---
Hello again,
I'm sending this patch to bring virtual-keyboard back in line with the v3 of
the patc
On Fri, 20 Jul 2018 20:03:24 +0100
Daniel Stone wrote:
> From: Pekka Paalanen
>
> weston_debug is both a libweston API for relaying debugging messages,
> and the compositor-debug wayland protocol implementation for accessing those
> debug messages from a Wayland client.
>
> weston_debug_compos
On Thu, Aug 2, 2018 at 8:37 PM Michal Srb wrote:
>
> The length field can be any uint32 value. Two kinds of overflows may
> happen on 32 bit systems:
>
> 1) If the value is in range [UINT32_MAX-3, UINT32_MAX], the DIV_ROUNDUP
> will turn it into 0. Then `next` equals `p` and so the big `length` is
Hi Markus,
I am using the same parameters for socketpair. Here is my actual code:
static int
exec_wayland_client(const char *path, int fd)
{
if (seteuid(getuid()) == -1) {
return -1;
}
//unblock all the signals
sigset_t allsignals;
sigfill
> On Sat, Jul 28, 2018 at 8:15 PM, Sichem Zhou wrote:
>
> > Dear Weston devs:
> >
> > Sorry for the bothering in when weston-5.0 is approaching, but I am stuck
> > in the project for three days I need some one's help very much.
> >
> > I have a widget implementation of shell widgets that destroys
libxkbcommon 0.8.1
==
- Fix various problems found in the meson build (see commit messages for more
details):
- Fix compilation on Darwin.
- Fix compilation of the x11 tests and demos when XCB is installed in a
non-standard location.
- Fix xkbcommon-x11.pc mi
On Sat, 14 Jul 2018 14:09:07 +0100
Daniel Stone wrote:
> Though Wayland and the protocols still use mail-based patch review,
> Weston can now move to GitLab MRs with review through that system.
>
> Add some documentation on how to submit patches through GitLab,
> specifically targeted at people
On Sat, 14 Jul 2018 14:09:06 +0100
Daniel Stone wrote:
> Move the README file to Markdown, and update it to attempt to explain
> the current status and use of Weston.
>
> The first sections are user-facing, so they can quickly understand what
> Weston is, what it does, what it doesn't do, and ho
Hi Daniel,
El 03/08/18 a las 10:41, Daniel Stone escribió:
Hi Santiago,
On Fri, 3 Aug 2018 at 09:28, Santiago Otero wrote:
El 03/08/18 a las 09:35, Pekka Paalanen escribió:
No, you cannot use another KMS application at the same time as Weston
is active. The kernel DRM core will forbid access
On Fri, 20 Jul 2018 12:26:22 +0100
Daniel Stone wrote:
> Hi Deepak,
>
> On Fri, 20 Jul 2018 at 12:21, Deepak Singh Rawat wrote:
> > In brief the damage is in frame-buffer coordinate of attached fb to the
> > plane.
> > Unlike plane src coordinates, damage clips are not in 16.16 fixed point.
>
Hi Harsha,
On Tue, 24 Jul 2018 at 10:11, Harsha Manjula Mallikarjun (RBEI/ECF3)
wrote:
> > So, I understand this would be a manual test where the user would
> > visually verify that the gamma is changing in the way they would
> > expect? I have no problem with that, but it would be nice to see th
Hi Santiago,
On Fri, 3 Aug 2018 at 09:28, Santiago Otero wrote:
> El 03/08/18 a las 09:35, Pekka Paalanen escribió:
>> No, you cannot use another KMS application at the same time as Weston
>> is active. The kernel DRM core will forbid access (denies DRM Master
>> status) if there is already somet
Hi,
On Fri, 3 Aug 2018 at 09:21, Pekka Paalanen wrote:
> On Mon, 16 Jul 2018 14:14:33 -0300 Matheus Santana wrote:
> > There is an issue for this: https://gitlab.freedesktop.
> > org/wayland/wayland/issues/48
> >
> > For now, this series builds wayland within the site's pipeline by cloning
> > t
El 03/08/18 a las 09:35, Pekka Paalanen escribió:
On Thu, 12 Jul 2018 13:49:06 +0200
Santiago Otero wrote:
Hi all,
I have a display device that supports up to three different display
buffers: one graphic layer and two video layers. The graphic layer is at
the top (zpos=2).
I'm using Weston (
On Mon, 16 Jul 2018 14:14:33 -0300
Matheus Santana wrote:
> Hello!
>
> There is an issue for this: https://gitlab.freedesktop.
> org/wayland/wayland/issues/48
>
> For now, this series builds wayland within the site's pipeline by cloning
> the repository and building everything just like in wayl
On Thu, 12 Jul 2018 13:49:06 +0200
Santiago Otero wrote:
> Hi all,
>
> I have a display device that supports up to three different display
> buffers: one graphic layer and two video layers. The graphic layer is at
> the top (zpos=2).
>
> I'm using Weston (DRM backend) with a Qt5 application a
21 matches
Mail list logo