Fetch the repository succeeded.
<?xml version="1.0" encoding="UTF-8"?><protocol name="wlr_layer_shell_v1_unstable_v1"><copyright>Copyright © 2017 Drew DeVaultPermission to use, copy, modify, distribute, and sell thissoftware and its documentation for any purpose is hereby grantedwithout fee, provided that the above copyright notice appear inall copies and that both that copyright notice and this permissionnotice appear in supporting documentation, and that the name ofthe copyright holders not be used in advertising or publicitypertaining to distribution of the software without specific,written prior permission. The copyright holders make norepresentations about the suitability of this software for anypurpose. It is provided "as is" without express or impliedwarranty.THE COPYRIGHT HOLDERS DISCLAIM ALL WARRANTIES WITH REGARD TO THISSOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS, IN NO EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANYSPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGESWHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER INAN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OFTHIS SOFTWARE.</copyright><interface name="zwlr_layer_shell_v1" version="1"><description summary="create surfaces that are layers of the desktop">Clients can use this interface to assign the surface_layer role towl_surfaces. Such surfaces are assigned to a "layer" of the output andrendered with a defined z-depth respective to each other. They may also beanchored to the edges and corners of a screen and specify input handlingsemantics. This interface should be suitable for the implementation ofmany desktop shell components, and a broad number of other applicationsthat interact with the desktop.</description><request name="get_layer_surface"><description summary="create a layer_surface from a surface">Create a layer surface for an existing surface. This assigns the role oflayer_surface, or raises a protocol error if another role is alreadyassigned.Creating a layer surface from a wl_surface which has a buffer attachedor committed is a client error, and any attempts by a client to attachor manipulate a buffer prior to the first layer_surface.configure callmust also be treated as errors.You may pass NULL for output to allow the compositor to decide whichoutput to use. Generally this will be the one that the user mostrecently interacted with.Clients can specify a namespace that defines the purpose of the layersurface.</description><arg name="id" type="new_id" interface="zwlr_layer_surface_v1"/><arg name="surface" type="object" interface="wl_surface"/><arg name="output" type="object" interface="wl_output" allow-null="true"/><arg name="layer" type="uint" enum="layer" summary="layer to add this surface to"/><arg name="namespace" type="string" summary="namespace for the layer surface"/></request><enum name="error"><entry name="role" value="0" summary="wl_surface has another role"/><entry name="invalid_layer" value="1" summary="layer value is invalid"/><entry name="already_constructed" value="2" summary="wl_surface has a buffer attached or committed"/></enum><enum name="layer"><description summary="available layers for surfaces">These values indicate which layers a surface can be rendered in. Theyare ordered by z depth, bottom-most first. Traditional shell surfaceswill typically be rendered between the bottom and top layers.Fullscreen shell surfaces are typically rendered at the top layer.Multiple surfaces can share a single layer, and ordering within asingle layer is undefined.</description><entry name="background" value="0"/><entry name="bottom" value="1"/><entry name="top" value="2"/><entry name="overlay" value="3"/></enum></interface><interface name="zwlr_layer_surface_v1" version="1"><description summary="layer metadata interface">An interface that may be implemented by a wl_surface, for surfaces thatare designed to be rendered as a layer of a stacked desktop-likeenvironment.Layer surface state (size, anchor, exclusive zone, margin, interactivity)is double-buffered, and will be applied at the time wl_surface.commit ofthe corresponding wl_surface is called.</description><request name="set_size"><description summary="sets the size of the surface">Sets the size of the surface in surface-local coordinates. Thecompositor will display the surface centered with respect to itsanchors.If you pass 0 for either value, the compositor will assign it andinform you of the assignment in the configure event. You must set youranchor to opposite edges in the dimensions you omit; not doing so is aprotocol error. Both values are 0 by default.Size is double-buffered, see wl_surface.commit.</description><arg name="width" type="uint"/><arg name="height" type="uint"/></request><request name="set_anchor"><description summary="configures the anchor point of the surface">Requests that the compositor anchor the surface to the specified edgesand corners. If two orthoginal edges are specified (e.g. 'top' and'left'), then the anchor point will be the intersection of the edges(e.g. the top left corner of the output); otherwise the anchor pointwill be centered on that edge, or in the center if none is specified.Anchor is double-buffered, see wl_surface.commit.</description><arg name="anchor" type="uint" enum="anchor"/></request><request name="set_exclusive_zone"><description summary="configures the exclusive geometry of this surface">Requests that the compositor avoids occluding an area of the surfacewith other surfaces. The compositor's use of this information isimplementation-dependent - do not assume that this region will notactually be occluded.A positive value is only meaningful if the surface is anchored to anedge, rather than a corner. The zone is the number of surface-localcoordinates from the edge that are considered exclusive.Surfaces that do not wish to have an exclusive zone may instead specifyhow they should interact with surfaces that do. If set to zero, thesurface indicates that it would like to be moved to avoid occludingsurfaces with a positive excluzive zone. If set to -1, the surfaceindicates that it would not like to be moved to accommodate for othersurfaces, and the compositor should extend it all the way to the edgesit is anchored to.For example, a panel might set its exclusive zone to 10, so thatmaximized shell surfaces are not shown on top of it. A notificationmight set its exclusive zone to 0, so that it is moved to avoidoccluding the panel, but shell surfaces are shown underneath it. Awallpaper or lock screen might set their exclusive zone to -1, so thatthey stretch below or over the panel.The default value is 0.Exclusive zone is double-buffered, see wl_surface.commit.</description><arg name="zone" type="int"/></request><request name="set_margin"><description summary="sets a margin from the anchor point">Requests that the surface be placed some distance away from the anchorpoint on the output, in surface-local coordinates. Setting this valuefor edges you are not anchored to has no effect.The exclusive zone includes the margin.Margin is double-buffered, see wl_surface.commit.</description><arg name="top" type="int"/><arg name="right" type="int"/><arg name="bottom" type="int"/><arg name="left" type="int"/></request><request name="set_keyboard_interactivity"><description summary="requests keyboard events">Set to 1 to request that the seat send keyboard events to this layersurface. For layers below the shell surface layer, the seat will usenormal focus semantics. For layers above the shell surface layers, theseat will always give exclusive keyboard focus to the top-most layerwhich has keyboard interactivity set to true.Layer surfaces receive pointer, touch, and tablet events normally. Ifyou do not want to receive them, set the input region on your surfaceto an empty region.Events is double-buffered, see wl_surface.commit.</description><arg name="keyboard_interactivity" type="uint"/></request><request name="get_popup"><description summary="assign this layer_surface as an xdg_popup parent">This assigns an xdg_popup's parent to this layer_surface. This popupshould have been created via xdg_surface::get_popup with the parent setto NULL, and this request must be invoked before committing the popup'sinitial state.See the documentation of xdg_popup for more details about what anxdg_popup is and how it is used.</description><arg name="popup" type="object" interface="xdg_popup"/></request><request name="ack_configure"><description summary="ack a configure event">When a configure event is received, if a client commits thesurface in response to the configure event, then the clientmust make an ack_configure request sometime before the commitrequest, passing along the serial of the configure event.If the client receives multiple configure events before itcan respond to one, it only has to ack the last configure event.A client is not required to commit immediately after sendingan ack_configure request - it may even ack_configure several timesbefore its next surface commit.A client may send multiple ack_configure requests before committing, butonly the last request sent before a commit indicates which configureevent the client really is responding to.</description><arg name="serial" type="uint" summary="the serial from the configure event"/></request><request name="destroy" type="destructor"><description summary="destroy the layer_surface">This request destroys the layer surface.</description></request><event name="configure"><description summary="suggest a surface change">The configure event asks the client to resize its surface.Clients should arrange their surface for the new states, and then sendan ack_configure request with the serial sent in this configure event atsome point before committing the new surface.The client is free to dismiss all but the last configure event itreceived.The width and height arguments specify the size of the window insurface-local coordinates.The size is a hint, in the sense that the client is free to ignore it ifit doesn't resize, pick a smaller size (to satisfy aspect ratio orresize in steps of NxM pixels). If the client picks a smaller size andis anchored to two opposite anchors (e.g. 'top' and 'bottom'), thesurface will be centered on this axis.If the width or height arguments are zero, it means the client shoulddecide its own window dimension.</description><arg name="serial" type="uint"/><arg name="width" type="uint"/><arg name="height" type="uint"/></event><event name="closed"><description summary="surface should be closed">The closed event is sent by the compositor when the surface will nolonger be shown. The output may have been destroyed or the user mayhave asked for it to be removed. Further changes to the surface will beignored. The client should destroy the resource after receiving thisevent, and create a new surface if they so choose.</description></event><enum name="error"><entry name="invalid_surface_state" value="0" summary="provided surface state is invalid"/><entry name="invalid_size" value="1" summary="size is invalid"/><entry name="invalid_anchor" value="2" summary="anchor bitfield is invalid"/></enum><enum name="anchor" bitfield="true"><entry name="top" value="1" summary="the top edge of the anchor rectangle"/><entry name="bottom" value="2" summary="the bottom edge of the anchor rectangle"/><entry name="left" value="4" summary="the left edge of the anchor rectangle"/><entry name="right" value="8" summary="the right edge of the anchor rectangle"/></enum></interface></protocol>