On Thu, Aug 02, 2018 at 10:29:53AM +0200, Quentin Glidic wrote:
> From: Quentin Glidic
>
> If we start a special (grabbing) client when Weston is unfocused, it
> would lose focus when coming back to Weston.
>
> A first attempt to fix this was 85d55540cb64bf97a08b40f79dc66843f8295d3b
> but it
On 2018/7月/11 09:42, Sichem Zhou wrote:
> Hi All,
>
> I have a question related to the wl_client creation in the compositor. I
> followed these step like weston did:
>
> 1. create socketpair.
> 2. fork a process and close `socket[0]` in child, close `socket[1]` in in
> parent process.
> 3. set
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_config which already has the matching config but ensure that
windows and
Hi Daniel,
Thanks for the detailed explanation, I will send v2 patch.
Thanks
Mads
-Original Message-
From: Daniel Stone [mailto:dan...@fooishbar.org]
Sent: Thursday, August 02, 2018 5:35 AM
To: Madhurkiran Harikrishnan
Cc: wayland ; nofooter
Subject: Re: [prefix=PATCH weston]
Dear all,
I solved it using the `frame_signal` in the weston_output. I referenced the
Weston shell `set_minimized` implementation, which works by moving view to
a hidden layer. It didn't work for me since I trigger immediately the next
frame once moving the view back to the original layer. The
On Wed, 11 Jul 2018 21:42:24 -0400
Sichem Zhou wrote:
> Hi All,
>
> I have a question related to the wl_client creation in the compositor. I
> followed these step like weston did:
>
> 1. create socketpair.
> 2. fork a process and close `socket[0]` in child, close `socket[1]` in in
> parent
Hi Madhurkiran,
On Tue, 31 Jul 2018 at 02:02, Madhurkiran Harikrishnan
wrote:
> Thanks for the comments. For a not having configless_context, can you
> explain why should I check gr->egl_config, because the attributes passed
> while getting this gr->egl_config does not have EGL_PBUFFER_BIT
On 8/2/18 10:29 AM, Quentin Glidic wrote:
From: Quentin Glidic
If we start a special (grabbing) client when Weston is unfocused, it
would lose focus when coming back to Weston.
A first attempt to fix this was 85d55540cb64bf97a08b40f79dc66843f8295d3b
but it messed with VT switching.
This fix
From: Quentin Glidic
If we start a special (grabbing) client when Weston is unfocused, it
would lose focus when coming back to Weston.
A first attempt to fix this was 85d55540cb64bf97a08b40f79dc66843f8295d3b
but it messed with VT switching.
This fix just updates the saved focus, so when Weston
From: Quentin Glidic
This reverts commit 85d55540cb64bf97a08b40f79dc66843f8295d3b.
It brought issues for proper VT switching focus handling.
Signed-off-by: Quentin Glidic
---
libweston/input.c | 26 +++---
1 file changed, 11 insertions(+), 15 deletions(-)
diff --git
On Thu, 2 Aug 2018, 09:14 Peter Hutterer, wrote:
>
> nah, not without scaling. The device always reports in integers only, but
> those integers have a physical reference point - the resolution of the
> device in DPI.
Ah right I understand now!
Thanks for your time and sorry about the noise.
On Thu, Aug 02, 2018 at 08:20:38AM +0200, Josh Simmons wrote:
> On Thu, Aug 2, 2018 at 7:49 AM, Peter Hutterer
> wrote:
> >
> > and since devices don't give you anything < 1 unit delta, subpixel isn't
> > really a thing unless you lower the speed setting.
> >
>
> So perhaps I'm missing
On Thu, Aug 2, 2018 at 7:49 AM, Peter Hutterer wrote:
>
> and since devices don't give you anything < 1 unit delta, subpixel isn't
> really a thing unless you lower the speed setting.
>
So perhaps I'm missing something, but the raw events as reported by
libinput debug-events do in fact have
13 matches
Mail list logo
