On 10 July 2018 6:03:26 pm AEST, David Edmundson
wrote:
>>Hm. If you wanted to, you could make this explicit by requiring an
>event serial in the export_surface request rather than the wl_surface.
>
>Certainly an option. Though I'm not sure we have a use case of needing
>to limit a client releasi
On Fri, Jul 6, 2018 at 1:26 AM, David Edmundson
wrote:
This protocol is to address the following use case.
A user clicks on a URL link in an IRC chat and a web browser opens.
We want an existing browser window to raise or if it's a newly
spawned application to claim focus on startup.
Nat
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 ---
1 file changed, 16 insertions(+), 7 deletions(-)
diff --gi
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 a
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 such code will detect internal server error
From: Christopher James Halse Rogers
Signed-off-by: Christopher James Halse Rogers
---
src/wayland-server-core.h | 59 +++
1 file changed, 59 insertions(+)
diff --git a/src/wayland-server-core.h b/src/wayland-server-core.h
index 61da8ab..0a2c689 100
