Copyright © 2018 Simon Ser Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice (including the next paragraph) shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. This protocol allows compositors to advertize XCursor configuration to clients. Once compositor configuration is received, clients are responsible for loading the XCursor theme, creating wl_buffers with cursor images and setting the cursor. Clients are free to ignore configuration set by this protocol and use different settings: this protocol merely exposes hints. Warning! The protocol described in this file is experimental and backward incompatible changes may be made. Backward compatible changes may be added together with the corresponding interface version bump. Backward incompatible changes are done by bumping the version number in the protocol and interface names and resetting the interface version. Once the protocol is to be declared stable, the 'z' prefix and the version number in the protocol and interface names are removed and the interface version number is reset. A global factory interface for wp_xcursor_configuration objects. Destroy the XCursor configuration manager. This doesn't destroy objects created with the manager. Describes input devices that have a cursor and are attached to a seat. This creates a new wp_xcursor_configuration object for the input device attached to the given seat. A Xcursor configuration object describes XCursor settings for a specific device. Using this request a client can tell the server that it is not going to use this object anymore. This event is sent after all other properties of a wp_xcursor_configuration have been sent. This allows changes to the wp_xcursor_configuration properties to be seen as atomic, even if they happen via multiple events. The theme event describes XCursor theme configuration for this device. The default_cursor event describes the default XCursor cursor name to be used for this device.