package oxbow
Install
dune-project
Dependency
Authors
Maintainers
Sources
md5=a182e6d368a65e6752771e41e651713f
sha512=020d2c7f9f4e06966ca56695e24eb0b41dd12500aa65d2cd9b56e03068bbb6ea7770de0a33c04f0d054bd474bee8c2b36bb46af86266c9823490e1bd0810c027
doc/oxbow.river/River/Server/Input/Management/River_input_device_v1/index.html
Module Management.River_input_device_v1Source
An input device.
An input device represents a physical keyboard, mouse, touchscreen, or drawing tablet tool. It is assigned to exactly one seat at a time. By default, all input devices are assigned to the default seat.
Version 1
The name of the input device.
The name of the input device. This event is sent once when the river_input_device_v1 object is created. The device name cannot change during the lifetime of the object.
The type of the input device.
The type of the input device. This event is sent once when the river_input_device_v1 object is created. The device type cannot change during the lifetime of the object.
The input device is removed.
This event indicates that the input device has been removed.
The server will send no further events on this object and ignore any request (other than river_input_device_v1.destroy) made after this event is sent. The client should destroy this object with the river_input_device_v1.destroy request to free up resources.
Version 2
All information has been sent.
This event is sent after all information about the input device has been sent.
This allows changes to one or more river_input_device_v1 properties to be seen as atomic, even if they happen via multiple events.
Handlers
Note: Servers will always want to use v1.