package oxbow
Install
dune-project
Dependency
Authors
Maintainers
Sources
md5=a637acaa0e19046cd65fff733874eb97
sha512=76230cbecd7510de7a05b5d1f335915ef7b6c4aa557d8dbfd23591606618d2cfa25082d17b93f2f4b53a118d1cbf6a80e4ad51cf0f099b4921fb83d6df0c9801
doc/oxbow.river/River/Obj/Window_management/C/River_pointer_binding_v1/index.html
Module C.River_pointer_binding_v1Source
Configure a pointer binding, receive trigger events.
This object allows the window manager to configure a pointer binding and receive events when the binding is triggered.
The new pointer binding is not enabled until the enable request is made during a manage sequence.
Normally, all pointer button events are sent to the surface with pointer focus by the compositor. Pointer button events that trigger a pointer binding are not sent to the surface with pointer focus.
If multiple pointer bindings would be triggered by a single physical pointer event on the compositor side, it is compositor policy which pointer binding(s) will receive press/release events or if all of the matched pointer bindings receive press/release events.
Version 1, 2, 3, 4, 5
Disable the pointer binding.
This request may be used to temporarily disable the pointer binding. It may be later re-enabled with the enable request.
This request modifies window management state and may only be made as part of a manage sequence, see the river_window_manager_v1 description.
Enable the pointer binding.
This request should be made after all initial configuration has been completed and the window manager wishes the pointer binding to be able to be triggered.
This request modifies window management state and may only be made as part of a manage sequence, see the river_window_manager_v1 description.
Destroy the pointer binding object.
This request indicates that the client will no longer use the pointer binding object and that it may be safely destroyed.
Handlers
Note: Servers will always want to use v1.