From: Christopher James Halse Rogers
This will allow other wrappers around wl_resource_post_error to accept
variable argument lists.
Signed-off-by: Christopher James Halse Rogers
---
src/wayland-server.c | 23
Because C++ exceptions escaping into C FFI invokes undefined behaviour
our Wayland implementation wraps all the interface vtable callbacks
with try {} catch (...) { log_error }.
This has the nice property of not crashing the server, but does result
in the client and server having different ideas
From: Christopher James Halse Rogers
Many languages such as C++ or Rust have an unwinding error-reporting
mechanism. Code in these languages can (and must!) wrap request handling
callbacks in unwind guards to avoid undefined behaviour.
As a consequence
On Sun, Feb 18, 2018 at 11:14:55PM +0300, Konstantin Kharlamov wrote:
> The details are explained in comment in the code. That aside, I shall
> mention the check is so light, that it shouldn't influence CPU
> performance even a bit, and can blindly be kept always enabled.
I like it! And it does
If a single-touch touchpad drops below the pressure threshold in the same
frame where a fake finger is added, we begin a fake touch here. The subsequent
loop ends this fake touch because real_fingers_down is 0.
This causes the tapping code to have a mismatch of how many fingers are down
because
FWIW, given peoples complained about hysteresis algo latency, I'm also
poking around with alternative hysteresis algos. One possible idea that
came to my mind is to use the detection code posted here to figure the
maximum wobbliness length (along each axis separately), then simply
ignore
From: Quentin Glidic
Signed-off-by: Quentin Glidic
---
libweston/compositor-x11.c | 64 +-
1 file changed, 29 insertions(+), 35 deletions(-)
diff --git a/libweston/compositor-x11.c
From: Quentin Glidic
We discussed on IRC about races between the several event sources that
exist in libweston, libwayland and compositor code. Adding a priority
system in the event loop is a first step to fix these potential races
and help cope with bad clients.
A
From: Quentin Glidic
This will allow compositors to pick any event loop implementation they
want, and integrating the libweston components with it.
Specifically, idle and timeout sources can now have proper priorities to
avoid being ghosted by client event
Commit 332d1892 introduced a bug because the window was
shaped only when the frame was created, leaving the input
region unchanged regardless if the window was resized.
This patch updates the input region shape on resize,
fixing the problem.
---
xwayland/window-manager.c | 46
Was crashing when I tried to take a screenshot.
---
On my slightly unconventional setup (FreeBSD amdgpu), after merging
recent changes, pressing the screenshot hotkey was crashing weston.
Debugging revealed that cursor_plane was 0x0 here.
I don't know why exactly, but adding this check fixes it.
On Sun, Feb 18, 2018 at 01:09:22PM +0300, Konstantin Kharlamov wrote:
> For the purposes it seems to work fine — it's marked RFC because I see a
> small oddness, and I think it's better to ask someone more
> acknowledgable in libinput codebase.
thanks, much appreciated. I was hoping I get to this
12 matches
Mail list logo