package wayland
Pure OCaml Wayland protocol library
Install
Dune Dependency
Authors
Maintainers
Sources
wayland-2.0.tbz
sha256=8821b5ce4d6d03b81d186b7bf1cdec422d0d37d161dc7b023f8732ed8de9834b
sha512=d948ef44fefd3aed4c3a89cc2bea82e3e7ef6ef8584516645e763c2e5dbc31683c2f45fb002a1a22072ad7221972ad28f032973e9d40ae470b425c460c51ecdf
doc/wayland.protocols/Wayland_protocols/Xdg_shell_client/Xdg_wm_base/class-v3/index.html
Class Xdg_wm_base.v3
Source
Handler for a proxy with version >= 3.
constraint 'a = [< `V3 | `V4 | `V5 | `V6 ]
method private virtual on_ping : [> `V3 | `V4 | `V5 | `V6 ] t ->
serial:int32 ->
unit
Check if the client is alive.
The ping event asks the client if it's still alive. Pass the serial specified in the event back to the compositor by sending a "pong" request back with the specified serial. See xdg_wm_base.pong.
Compositors can use this to determine if the client is still alive. It's unspecified what will happen if the client doesn't respond to the ping request, or in what timeframe. Clients should try to respond in a reasonable amount of time. The “unresponsive” error is provided for compositors that wish to disconnect unresponsive clients.
A compositor is free to ping in any way it wants, but a client must always respond to any xdg_wm_base object it created.
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>