blob: c94c40ce38a4550bf3d1acc32988350b22500fd3 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<protocol name="aura_shell">
<copyright>
Copyright 2017 The Chromium Authors
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.
</copyright>
<interface name="zaura_shell" version="63">
<description summary="aura_shell">
The global interface exposing aura shell capabilities is used to
instantiate an interface extension for a wl_surface object.
This extended interface will then allow the client to use aura shell
specific functionality.
</description>
<enum name="error">
<entry name="aura_surface_exists" value="0"
summary="the surface already has an aura surface object associated"/>
<entry name="aura_output_exists" value="1"
summary="the output already has an aura output object associated"/>
</enum>
<request name="get_aura_surface">
<description summary="extend surface interface for aura shell">
Instantiate an interface extension for the given wl_surface to
provide aura shell functionality. If the given wl_surface is not
associated with a shell surface, the shell_surface_missing protocol
error is raised.
</description>
<arg name="id" type="new_id" interface="zaura_surface"
summary="the new aura surface interface id"/>
<arg name="surface" type="object" interface="wl_surface"
summary="the surface"/>
</request>
<!-- Version 2 additions -->
<request name="get_aura_output" since="2">
<description summary="extend output interface for aura shell">
Instantiate an interface extension for the given wl_output to
provide aura shell functionality.
</description>
<arg name="id" type="new_id" interface="zaura_output"
summary="the new aura output interface id"/>
<arg name="output" type="object" interface="wl_output"
summary="the output"/>
</request>
<!-- Version 11 additions -->
<enum name="layout_mode">
<description summary="the layout mode">
Specifies the server's window layout mode.
</description>
<entry name="windowed" value="1" summary="multiple windows"/>
<entry name="tablet" value="2" summary="restricted mode for tablet"/>
</enum>
<event name="layout_mode" since="11">
<description summary="sends the layout_mode">
Sends the layout_mode used by the server.
</description>
<arg name="layout_mode" type="uint" summary="layout_mode enum"/>
</event>
<!-- Version 14 additions -->
<event name="bug_fix" since="14">
<description summary="sends a bug fix ID">
Sends a monorail ID of a bug fixed on the exo server that clients can
use to gate functionality.
</description>
<arg name="id" type="uint" summary="ID of a single bug fix"/>
</event>
<event name="desks_changed" since="22">
<description summary="sends names of desks">
Notifies when there is a change in global desks state. This is emitted on
desk name changes, desk addition/removal or desks are reordered.
"desk_names" argument contains the set of null terminated strings as names of desks.
</description>
<arg name="desk_names" type="array" summary="an array of existing desks' names"/>
</event>
<event name="desk_activation_changed" since="22">
<description summary="sends the index of the active desk">
Notifies when there is a change of the active desk.
</description>
<arg name="active_desk_index" type="int" summary="index of the active desk"/>
</event>
<!-- Version 24 additions -->
<event name="activated" since="24">
<description summary="activated surface changed">
Notifies client that the activated surface changed.
</description>
<arg name="gained_active" type="object" interface="wl_surface" allow-null="true"/>
<arg name="lost_active" type="object" interface="wl_surface" allow-null="true"/>
</event>
<!-- Version 26 additions -->
<request name="surface_submission_in_pixel_coordinates" since="26">
<description summary="surfaces will be submitted in pixel coordinates">
[Deprecated] Informs the server that when submitting surfaces, this
client will not use wl_surface_set_buffer_scale to report the scales,
nor will it apply scale via vp_viewporter. Instead the server should
apply an appropriate scale transform to have the submitted buffers
composited correctly.
</description>
</request>
<request name="get_aura_toplevel_for_xdg_toplevel" since="27">
<description summary="get aura toplevel">
Retrieve the aura toplevel interface for a given xdg toplevel interface
</description>
<arg name="id" type="new_id" interface="zaura_toplevel"
summary="the new aura toplevel interface id"/>
<arg name="toplevel" type="object" interface="xdg_toplevel"/>
</request>
<request name="get_aura_popup_for_xdg_popup" since="28">
<description summary="get aura popup">
Retrieve the aura popup interface for the given xdg popup interface
</description>
<arg name="id" type="new_id" interface="zaura_popup"
summary="the aura popup interface id"/>
<arg name="popup" type="object" interface="xdg_popup"/>
</request>
<request name="release" type="destructor" since="38">
<description summary="release zaura_shell object">
Using this request a client can tell the server that it is not going to
use the zaura_shell object anymore. This does not affect any other objects.
This is named "release" because "destroy" is a special named function used for
freeing wl_proxy objects. Naming it "destroy" will cause marshalling errors
when running on lower versioned hosts. All "release" requests here should be
renamed to "destroy" if we move to aura-shell v2.
</description>
</request>
<!-- Version 57 additions -->
<event name="set_overview_mode" since="57">
<description summary="entered overview mode">
Notifies client that the server has entered overview mode. Overview mode
displays all app windows associated with the current desk for the user.
</description>
</event>
<event name="unset_overview_mode" since="57">
<description summary="exited overview mode">
Notifies client that the server has exited overview mode.
</description>
</event>
<!-- Version 58 additions -->
<event name="compositor_version" since="58">
<description summary="sends the server version">
Sends the Exo compositor version information.
</description>
<arg name="version_label" type="string" summary="version string label"/>
</event>
<!-- Version 60 additions -->
<event name="all_bug_fixes_sent" since="60">
<description summary="completed sending all bug fix ids">
Notifies client that all the IDs of a bug fixed on the exo server is
sent. Bug fix ids are sent via `bug_fix` events which sends ids one by
one, not an array. This event is used to confirm all ids are sent.
</description>
</event>
<!-- Version 61 additions -->
<event name="window_corners_radii" since="61">
<description summary="sends the radius of each corner the window">
Sends the radius of each corner of the window to the clients in dips.
</description>
<arg name="upper_left_radius" type="uint"/>
<arg name="upper_right_radius" type="uint"/>
<arg name="lower_right_radius" type="uint"/>
<arg name="lower_left_radius" type="uint"/>
</event>
</interface>
<interface name="zaura_surface" version="51">
<description summary="aura shell interface to a wl_surface">
An additional interface to a wl_surface object, which allows the
client to access aura shell specific functionality for surface.
</description>
<enum name="frame_type">
<description summary="different frame types">
Frame types that can be used to decorate a surface.
</description>
<entry name="none" value="0" summary="no frame"/>
<entry name="normal" value="1" summary="caption with shadow" />
<entry name="shadow" value="2" summary="shadow only"/>
</enum>
<request name="set_frame">
<description summary="request a frame for surface">
[Deprecated] Suggests a surface should use a specific frame. Deprecated
since M105. See the set_decoration method on zaura_toplevel and
zaura_popup.
</description>
<arg name="type" type="uint" summary="the new frame type"/>
</request>
<!-- Version 2 additions -->
<request name="set_parent" since="2">
<description summary="set the parent of this surface">
Set the "parent" of this surface. "x" and "y" arguments specify the
initial position for surface relative to parent.
</description>
<arg name="parent" type="object" interface="zaura_surface" allow-null="true"/>
<arg name="x" type="int"/>
<arg name="y" type="int"/>
</request>
<!-- Version 3 additions -->
<request name="set_frame_colors" since="3">
<description summary="set the frame colors of this surface">
Set the frame colors.
</description>
<arg name="active_color" type="uint" summary="32 bit ARGB color value, not premultiplied"/>
<arg name="inactive_color" type="uint" summary="32 bit ARGB color value, not premultiplied"/>
</request>
<!-- Version 4 additions -->
<request name="set_startup_id" since="4">
<description summary="set the startup ID of this surface">
Set the startup ID.
</description>
<arg name="startup_id" type="string" allow-null="true"/>
</request>
<!-- Version 5 additions -->
<request name="set_application_id" since="5">
<description summary="set the application ID of this surface">
Set the application ID.
</description>
<arg name="application_id" type="string" allow-null="true"/>
</request>
<!-- Version 7 additions -->
<request name="set_client_surface_id" since="7">
<description summary="set the client surface ID of this surface">
Deprecated. Please use set_client_surface_str_id instead.
Set the identifier of the surface assigned by the client.
</description>
<arg name="client_surface_id" type="int" />
</request>
<!-- Version 8 additions -->
<enum name="occlusion_change_reason">
<description summary="occlusion change reason">
Enum describing why an occlusion change happened. An occlusion change as a
result of a user action could include things like the user moving a window,
changing occlusion, or opening/closing a window, changing the occlusion.
</description>
<entry name="user_action" value="1" summary="occlusion changed as a result of a user action"/>
</enum>
<request name="set_occlusion_tracking" since="8">
<description summary="set tracked occlusion region">
Sets occlusion tracking on this surface. The client will be updated with a
new occlusion fraction when the amount of occlusion of this surface changes.
</description>
</request>
<request name="unset_occlusion_tracking" since="8">
<description summary="unset tracked occlusion region">
Unsets occlusion tracking for this surface.
</description>
</request>
<event name="occlusion_changed" since="8">
<description summary="Notifies on an occlusion change">
Notifies when there is a change in the amount this surface is occluded.
The occlusion update is sent as a fixed point number from 0 to 1, representing
the proportion of occlusion.
</description>
<arg name="occlusion_fraction" type="fixed"/>
<arg name="occlusion_reason" type="uint"/>
</event>
<!-- Version 9 additions -->
<request name="activate" since="9">
<description summary="Indicate that this window wants to be the active window">
[Deprecated] Make this the active window. This usually implies something
like restacking this surface to the foreground. The compositor is free
to ignore this request if it deems the client to be misbehaving.
Typically this request will only be honoured in response to some user
driven event, such as executing an application or opening a file in a
window that already exists.
</description>
</request>
<request name="draw_attention" since="9">
<description summary="Indicate that this window wants some of the user's attention">
Draw attention to this surface in a way that does not change the user's
focus. This usually means animating window decorations or taskbar icons.
The compositor can still ignore this request if it deems fit, but unlike
draw_focus, these requests are expected to come from background tasks,
and are more likely to be honoured.
</description>
</request>
<!-- Version 10 additions -->
<enum name="fullscreen_mode">
<description
summary="Specifies the behavior of the surface in fullscreen.">
[Deprecated] Possible windowing system behaviors if this surface were to go
fullscreen.
</description>
<entry
name="immersive"
value="0"
summary="user can access system UIs such as the shelf and window frame
by pointing to, or swiping over, the screen edge"/>
<entry
name="plain"
value="1"
summary="user cannot access system UIs using mouse/touches"/>
</enum>
<request name="set_fullscreen_mode" since="10">
<description summary="Sets the behavior of the surface in fullscreen.">
[Deprecated] Use the set_fullscreen_mode in the toplevel interface.
Suggests how the windowing system should behave if this surface were
to go fullscreen. Does not make the surface fullscreen.
Typically the default mode is "immersive".
</description>
<arg name="mode" type="uint" enum="fullscreen_mode"/>
</request>
<!-- Version 12 additions -->
<request name="set_client_surface_str_id" since="12">
<description summary="set the client surface ID of this surface">
Set the identifier of the surface assigned by the client.
</description>
<arg name="client_surface_id" type="string" />
</request>
<!-- Version 15 additions -->
<request name="set_server_start_resize" since="15">
<description summary="request a server-side shadow for surface">
Suggests a surface to have client-side decoration, but
server-side decides when and where to start the resize. The server may also
apply visual effects to indicate that the resize operation is ongoing.
</description>
</request>
<!-- Version 16 additions -->
<enum name="snap_direction">
<description summary="surface snap directions">
Surface snap directions.
</description>
<entry name="none" value="0" summary=""/>
<entry name="left" value="1" summary=""/>
<entry name="right" value="2" summary=""/>
</enum>
<request name="intent_to_snap" since="16">
<description summary="client intents to snap the surface.">
[Deprecated] Use intent_to_snap on zaura_toplevel.
Notify (or inform) the server the client's intent to snap the window.
To inform it's no longer willing to snap, send 'none'.
</description>
<arg name="direction" type="uint" enum="snap_direction"/>
</request>
<request name="set_snap_left" since="16">
<description summary="snap the surface to the left.">
[Deprecated] Use set_snap_primary on zaura_toplevel.
Request that surface is snapped to the left.
</description>
</request>
<request name="set_snap_right" since="16">
<description summary="snap the surface to the right.">
[Deprecated] Use set_snap_secondary on zaura_toplevel.
Request that surface is snapped to the right.
</description>
</request>
<request name="unset_snap" since="16">
<description summary="Unset the surface snap.">
[Deprecated] Use unset_snap on zaura_toplevel.
Request that surface resets snapping.
</description>
</request>
<!-- Version 17 additions -->
<event name="lock_frame_normal" since="17">
<description summary="Notify the client that server intent to lock window in normal or restore state">
Notifies the client to lock window in normal or restore state. When
window is locked, the window frame should look like it is in restored
state, but actually isn't. Locking happends while dragging a maximized
window.
</description>
</event>
<event name="unlock_frame_normal" since="17">
<description summary="Notify the client that server intent to unlock window's normal or restore state">
Notifies the client to unlock window if it is previously locked.
Unlocking happends while dragging a maximized window.
</description>
</event>
<!-- Version 18 additions -->
<request name="set_window_session_id" since="18">
<description summary="set surface window session id">
Set window session id to the surface.
</description>
<arg name="id" type="int" summary="window session id"/>
</request>
<!-- Version 19 additions -->
<request name="set_can_go_back" since="19">
<description summary="Set the minimize-on-back-gesture behavior.">
Sets that the surface can go back as per its navigation list.
This allows the server to react to by minimizing the window upon a
system wide back gesture.
</description>
</request>
<request name="unset_can_go_back" since="19">
<description summary="Unset the minimize-on-back-gesture behavior.">
Unsets that the surface can go back as per its navigation list.
See above.
</description>
</request>
<!-- Version 20 additions -->
<request name="set_pip" since="20">
<description summary="Set pip for the surface.">
Requests that the surface is set to Picture-in-Picture (PIP).
</description>
</request>
<request name="unset_pip" since="20">
<description summary="Unset pip for the surface.">
Requests that the surface is unset from Picture-in-Picture (PIP).
</description>
</request>
<request name="set_aspect_ratio" since="20">
<description summary="Set aspect ratio for the surface.">
Sets the aspect ratio of the surface.
</description>
<arg name="width" type="int"/>
<arg name="height" type="int"/>
</request>
<!-- Version 21 additions -->
<enum name="occlusion_state">
<description summary="surface occlusion state">
Describes the occlusion state of a surface.
</description>
<entry name="unknown" value="0" summary="The surface's occlusion state isn't tracked"/>
<entry name="visible" value="1" summary="The surface is visible"/>
<entry name="occluded" value="2" summary="The surface is occluded"/>
<entry name="hidden" value="3" summary="The surface is not visible"/>
</enum>
<event name="occlusion_state_changed" since="21">
<description summary="Notify the client that the occlusion state changed">
Notifies the client that the occlusion state of a window has changed. Clients
will only receive these messages if they previously request occlusion tracking
via set_occlusion_tracking for a particular surface.
</description>
<arg name="mode" type="uint" enum="occlusion_state"/>
</event>
<!-- Version 22 additions -->
<request name="move_to_desk" since="22">
<description summary="move to desk">
If |index| equals -1, requests that the server toggles whether client
is visible on all workspaces.
If |index| is not -1, requests that the server moves the client to the desk at
|index|.
</description>
<arg name="index" type="int"/>
</request>
<event name="desk_changed" since="22">
<description summary="window desk state changed">
Notifies when there is a change in the desk state of a window.
This is emitted when a window is moved to another desk or
when its assigned-to-all-desks state changes.
</description>
<arg name="state" type="int" summary="index of desk or -1 for a window assigned to all desks"/>
</event>
<!-- Version 23 additions -->
<request name="set_initial_workspace" since="23">
<description summary="initial workspace for restore">
If |initial_workspace| equals '-1', a window is restored and visible on all workspaces,
Otherwise, set the initial workspace to restore the window to the corresponding workspace.
This is not double buffered and must be set before attaching a buffer.
</description>
<arg name="initial_workspace" type="string" summary="intial workspace for restoring or '-1' for visible on all workspaces"/>
</request>
<!-- Version 25 additions -->
<request name="set_pin" since="25">
<description summary="pin a window (trusted or not)">
Requests that a window is pinned which means that the system does not allow
the user to leave the window until an exit criteria is met.
This is a request to get the window pinned so that the user cannot get to any
other window / application. There are two modes:
A. trusted is 0 - which is slightly less restrictive and allows the user to
get out of the window by a predefined way of authentication.
B. trusted is not 0 in which case a trusted application was locking down the
system and needs to unlock. This is used for e.g. School tests.
</description>
<arg name="trusted" type="int" summary="0 for non trusted"/>
</request>
<request name="unset_pin" since="25">
<description summary="unpin a window">
Requests that the user can leave a previously pinned window.
This is a request to unpin a previously pinned window. It does not matter if
the window was locked with the trusted state or not.
</description>
</request>
<event name="start_throttle" since="29">
<description summary="start throttling on the surface">
Informs the client to start throttling on the surface.
</description>
</event>
<event name="end_throttle" since="29">
<description summary="end throttling on the surface">
Informs the client to end throttling on the surface.
</description>
</event>
<!-- Version 38 additions -->
<request name="release" type="destructor" since="38">
<description summary="destroy zaura_surface">
Destroy the zaura_surface object. A client should destroy this object when the
role is unmapped from a wl_surface.
See zaura_shell.release for destructor naming.
</description>
</request>
<!-- Version 47 additions -->
<request name="show_tooltip" since="47">
<description summary="show tooltip window">
Show tooltip on server side.
`x` and `y` specifies the location of tooltip in surface local coordinates.
`hide_delay` and `show_delay` specify the time to wait until showing/hiding tooltip.
The unit is millisecond.
</description>
<arg name="text" type="string"/>
<arg name="x" type="int"/>
<arg name="y" type="int"/>
<arg name="tooltip_trigger" type="uint" summary="tooltip_trigger enum"/>
<arg name="show_delay" type="uint" summary="delay to show tooltip in millisecond"/>
<arg name="hide_delay" type="uint" summary="delay to hide tooltip in millisecond"/>
</request>
<enum name="tooltip_trigger">
<description summary="type of tooltip trigger">
Describes what triggered tooltip
</description>
<entry name="cursor" value="0" summary="triggered by cursor"/>
<entry name="keyboard" value="1" summary="triggered by keyboard"/>
</enum>
<request name="hide_tooltip" since="47">
<description summary="hide tooltip window">
Hide tooltip created by the same client on server side.
This may be called even when there is no tooltip window to hide.
</description>
</request>
<event name="tooltip_shown" since="47">
<description summary="tooltip is shown by server side">
Informs the client that the tooltip is shown with states.
`x` and `y` specifies the location of tooltip in surface local coordinates.
</description>
<arg name="text" type="string"/>
<arg name="x" type="int"/>
<arg name="y" type="int"/>
<arg name="width" type="int"/>
<arg name="height" type="int"/>
</event>
<event name="tooltip_hidden" since="47">
<description summary="tooltip is hidden by server side">
Informs the client that the tooltip is hidden.
</description>
</event>
<!-- Version 51 additions -->
<request name="set_accessibility_id" since="51">
<description summary="set accessibility ID to the surface">
Set accessibility window ID to the surface. A negative number removes
the existing accessibility ID from the surface.
</description>
<arg name="id" type="int" summary="Accessibility ID. Negative number removes existing accessibility ID from the surface."/>
</request>
</interface>
<interface name="zaura_output" version="45">
<description summary="aura shell interface to a wl_output">
An additional interface to a wl_output object, which allows the
client to access aura shell specific functionality for output.
</description>
<!-- Version 2 additions -->
<enum name="scale_property" bitfield="true">
<description summary="scale information">
These flags describe properties of an output scale.
They are used in the flags bitfield of the scale event.
</description>
<entry name="current" value="0x1"
summary="indicates this is the current scale"/>
<entry name="preferred" value="0x2"
summary="indicates this is the preferred scale"/>
</enum>
<enum name="scale_factor">
<entry name="0400" value="400"/>
<entry name="0500" value="500"/>
<entry name="0550" value="550"/>
<entry name="0600" value="600"/>
<entry name="0625" value="625"/>
<entry name="0650" value="650"/>
<entry name="0700" value="700"/>
<entry name="0750" value="750"/>
<entry name="0800" value="800"/>
<entry name="0850" value="850"/>
<entry name="0900" value="900"/>
<entry name="0950" value="950"/>
<entry name="1000" value="1000"/>
<entry name="1050" value="1050"/>
<entry name="1100" value="1100"/>
<entry name="1150" value="1150"/>
<entry name="1125" value="1125"/>
<entry name="1200" value="1200"/>
<entry name="1250" value="1250"/>
<entry name="1300" value="1300"/>
<entry name="1400" value="1400"/>
<entry name="1450" value="1450"/>
<entry name="1500" value="1500"/>
<entry name="1600" value="1600"/>
<entry name="1750" value="1750"/>
<entry name="1800" value="1800"/>
<entry name="2000" value="2000"/>
<entry name="2200" value="2200"/>
<entry name="2250" value="2250"/>
<entry name="2500" value="2500"/>
<entry name="2750" value="2750"/>
<entry name="3000" value="3000"/>
<entry name="3500" value="3500"/>
<entry name="4000" value="4000"/>
<entry name="4500" value="4500"/>
<entry name="5000" value="5000"/>
</enum>
<event name="scale" since="2">
<description summary="advertise available scales for the output">
The scale event describes an available scale for the output.
The event is sent when binding to the output object and there
will always be one scale, the current scale. The event is sent
again if an output changes scale, for the scale that is now
current. In other words, the current scale is always the last
scale that was received with the current flag set.
</description>
<arg name="flags" type="uint" enum="scale_property" summary="bitfield of scale flags"/>
<arg name="scale" type="uint" enum="scale_factor" summary="output scale"/>
</event>
<!-- Version 5 additions -->
<enum name="connection_type">
<entry name="unknown" value="0"/>
<entry name="internal" value="1"/>
</enum>
<event name="connection" since="5">
<description summary="advertise connection for the output">
The connection event describes how the output is connected.
The event is sent when binding to the output object.
</description>
<arg name="connection" type="uint" enum="connection_type" summary="output connection"/>
</event>
<event name="device_scale_factor" since="5">
<description summary="advertise device scale factor for the output">
This event describes the device specific scale factor for the output.
The device specific scale factor is not expected the change during
the lifetime of the output. And it is not limited to an integer value
like the scale factor provided by wl_output interface. The exact
contents scale used by the compositor can be determined by combining
this device scale factor with the current output scale.
The event is sent when binding to the output object.
</description>
<arg name="scale" type="uint" enum="scale_factor" summary="output device scale factor"/>
</event>
<!-- Version 33 additions -->
<event name="insets" since="33">
<description summary="advertise the work area insets for the output">
This event describes the insets for the output in logical screen
coordinates, from which the work area can be calculated.
This event is sent before wl_output.done, after which the client would
apply the change.
</description>
<arg name="top" type="int"/>
<arg name="left" type="int"/>
<arg name="bottom" type="int"/>
<arg name="right" type="int"/>
</event>
<!-- Version 34 additions -->
<event name="logical_transform" since="34">
<description summary="advertise the output's logical transform">
This event describes the logical transform for the output. Whereas
wl_output.geometry's transform corresponds to the display's panel
rotation, the logical transform corresponds to the display's logical
rotation.
This event is sent before wl_output.done, after which the client would
apply the change.
</description>
<arg name="transform" type="int" enum="wl_output.transform"/>
</event>
<!-- Version 38 additions -->
<request name="release" type="destructor" since="38">
<description summary="destroy zaura_output">
Destroy this zaura_shell object.
Destroying a bound zaura_shell object while there are zaura_surfaces
still alive created by this zaura_shell object instance is illegal
and will result in a protocol error.
See zaura_shell.release for destructor naming.
</description>
</request>
<event name="display_id" since="43">
<description summary="advertise the output's display id">
This event describes the 64bit display id assigned to each display by ChromeOS.
The value is opaque and should not be interpreted.
</description>
<arg name="display_id_hi" type="uint"/>
<arg name="display_id_lo" type="uint"/>
</event>
<!-- Version 45 additions -->
<event name="activated" since="45">
<description summary="target display for new windows">
Notifies that this output is now active output. It is typically used as a
target when a new window is created without specific bounds.
</description>
</event>
</interface>
<interface name="zaura_toplevel" version="63">
<description summary="aura shell interface to the toplevel shell">
An interface to the toplevel shell, which allows the
client to access shell specific functionality.
</description>
<enum name="orientation_lock">
<description summary="orientation lock request">
Defines orientation request when a surface is in fullscreen.
</description>
<entry name="none" value="1" summary="no orientation lock"/>
<entry name="portrait" value="2" summary="primary or secondary portrait"/>
<entry name="landscape" value="3" summary="primary or secondary landscape"/>
<entry name="current" value="4" summary="keep current orientation"/>
<entry name="portrait_primary" value="5" summary="primary portrait"/>
<entry name="landscape_primary" value="6" summary="primary landscape"/>
<entry name="portrait_secondary" value="7" summary="secondary portrait"/>
<entry name="landscape_secondary" value="8" summary="secondary landscape"/>
</enum>
<request name="set_orientation_lock" since="26">
<description summary="set orientation lock for a remote surface">
Request a specific orientation behavior when this surface is in fullscreen.
</description>
<arg name="orientation_lock" type="uint" enum="orientation_lock"/>
</request>
<request name="surface_submission_in_pixel_coordinates" since="28">
<description summary="surface will be submitted in pixel coordinates">
Informs the server that when submitting this surface, this client will not
use wl_surface_set_buffer_scale to report the scales, nor will it apply
scale via vp_viewporter. Instead the server should apply an appropriate
scale transform for the submitted buffers to be composited correctly.
</description>
</request>
<request name="set_supports_screen_coordinates" since="29">
<description summary="enables screen coordinates in window bounds">
Requesting this will enable screen coordinates in surfaces
associated with aura_toplevel including sub surfaces and popup
windows who added this toplevel as a parent. This should be
set before first commit.
</description>
</request>
<request name="set_window_bounds" since="29">
<description summary="set window size and position">
Request a new location and bounds of the surface in DP screen
coordinates. The size will be applied to visible bounds used
in set_geometry. The output is a hint for the compositor to
determine which output the window should move to. If the
output is null, the compositor should make decision solely by
the given bounds. These parameters are just a request and the
compositor may ignore, adjust the size and position based on
the rule imposed by the window manager, or may preserve it for
future operations. For example, the compositor will not allow
a position outside of the output, or the compositor may just
store it if the toplevel surface is in maximiezd state, and
may use it upon unmaximized.
</description>
<arg name="x" type="int"/>
<arg name="y" type="int"/>
<arg name="width" type="int"/>
<arg name="height" type="int"/>
<arg name="output" type="object" interface="wl_output" summary="the output" allow-null="true"/>
</request>
<event name="configure" since="29">
<description summary="suggest a surface change">
A configuration change that also includes the window origin in screen coordinates.
</description>
<arg name="x" type="int"/>
<arg name="y" type="int"/>
<arg name="width" type="int"/>
<arg name="height" type="int"/>
<arg name="states" type="array"/>
</event>
<enum name="state">
<description summary="supplemental aura states to xdg states">
The states that are contained here are supplemental to the states
defined in the XDG shell and specific aura windows.
</description>
<!-- Offset by 100 to prevent collision with new XDG states. -->
<entry name="immersive" value="100" since="36">
<description summary="immersive mode with hidden title bar and shelf">
User can access system UIs such as the shelf and window frame
by pointing to, or swiping over, the screen edge.
</description>
</entry>
<entry name="minimized" value="101" since="36">
<description summary="surface is minimized">
The window has been minimized.
</description>
</entry>
<entry name="snapped_primary" value="102" since="38">
<description summary="window is snapped in primary position">
The window is snapped to the left if the display is in landscape mode
and at the top in portrait mode.
</description>
</entry>
<entry name="snapped_secondary" value="103" since="38">
<description summary="window is snapped in secondary position">
The window is snapped to the right if the display is in landscape mode
and at the bottom in portrait mode.
</description>
</entry>
<entry name="floated" value="104" since="38">
<description summary="window is floated on top">
The window is floated on top of other windows. One floated window is
allowed per desk. Floating a window when there is already a floated
window on the same desk will unfloat the floated window.
</description>
</entry>
<entry name="pip" value="105" since="54">
<description summary="window is PiP">
The window is in PiP mode.
</description>
</entry>
</enum>
<event name="origin_change" since="29">
<description summary="window origin change">
A notification sent when the window origin has changed. Unlike a configure,
this does not imply the client needs to resize. The values are in screen
coordinates.
</description>
<arg name="x" type="int" />
<arg name="y" type="int" />
</event>
<request name="set_restore_info" since="30">
<description summary="set session id and restore id">
Request session id and restore id of a newly created browser window.
Set the information used by compositor to restore the toplevel
surface state, such as window position, window state, upon creation.
This is not double buffered and must be set before sending first commit.
</description>
<arg name="restore_session_id" type="int" summary="unique browser session id"/>
<arg name="restore_window_id" type="int" summary="restore browser window id"/>
</request>
<!-- Version 31 additions -->
<request name="set_system_modal" since="31">
<description summary="make window a system modal">
Requests that the toplevel surface should become a system modal. The
compositor will prevent other windows from receiving events. If there
are multiple system modal surfaces, the compositor will decide which
one to receive events.
</description>
</request>
<request name="unset_system_modal" since="31">
<description summary="unset window system modal state">
Requests that the system modal state of the toplevel surface will be
unset. The compositor will then allow other windows to recieve events.
</description>
</request>
<request name="set_restore_info_with_window_id_source" since="32">
<description summary="set session id and restore window id source">
Request session id and restore id of the window. Set the information used by compositor to restore the toplevel surface state, such as window position, window state, upon creation. This is not double buffered and must be set before sending first commit. This is different from set_restore_info, used for clients that create multiple windows associated with restore_id_source.
</description>
<arg name="restore_session_id" type="int" summary="unique browser session id"/>
<arg name="restore_window_id_source" type="string" summary="restore window id source"/>
</request>
<request name="set_decoration" since="35">
<description summary="request a decoration for surface">
Clients are allowed to request a particular decoration for a
zaura_toplevel. The server is not required to honor this request. See
decoration_type for available options. Available since M105.
</description>
<arg name="type" type="uint" summary="the new frame type"/>
</request>
<enum name="decoration_type">
<description summary="different decoration types">
Decoration types are used to modify the surface (e.g. drop shadow).
</description>
<entry name="none" value="0" summary="no frame"/>
<entry name="normal" value="1" summary="caption with shadow"/>
<entry name="shadow" value="2" summary="shadow only"/>
</enum>
<!-- Version 38 additions -->
<request name="release" type="destructor" since="38">
<description summary="destroy zaura_toplevel">
Destroy this zaura_toplevel object. A client should call destroy when the role
is unmapped from a wl_surface.
See zaura_shell.release for destructor naming.
</description>
</request>
<!-- Version 39 additions -->
<request name="set_float" since="39">
<description summary="float the surface on top">
[Deprecated] Use set_float_to_location.
This is a request to place the surface above others.
</description>
</request>
<request name="unset_float" since="39">
<description summary="unset the surface float">
Request that the surface resets floating.
</description>
</request>
<!-- version 40 additions -->
<request name="set_z_order" since="40">
<description summary="set z order for window">
Sets the z order for a toplevel surface. See z_order_level for available options.
</description>
<arg name="z_order" type="uint" summary="z order value for the window"/>
</request>
<enum name="z_order_level">
<description summary="z order levels for windows">
Different z order levels that are used to set the z order for a toplevel surface.
</description>
<entry name="normal" value="0" summary="the default level for windows"/>
<entry name="floating_window" value="1" summary="a floating window z-ordered above other normal windows"/>
<entry name="floating_ui_element" value="2" summary="used to show non-window style UIs that are shown above floating windows"/>
<entry name="security_surface" value="3" summary="cannot be interfered with or covered up"/>
</enum>
<!-- version 41 additions -->
<request name="set_origin" since="41">
<description summary="set window position in DPs">
Request a new location for the surface in device-independent pixels
(DPs), relative to the top-left corner of the given output.
A null output means whichever output currently contains the surface.
These parameters are just a request and the compositor may ignore
them, adjust them due to rules imposed by the window manager, or
preserve them for future operations. For example, the compositor will
not allow a position outside of the output; or the compositor may just
store it if the toplevel surface is in maximized state, and may use it
upon unmaximize.
</description>
<arg name="x" type="int"/>
<arg name="y" type="int"/>
<arg name="output" type="object" interface="wl_output" allow-null="true"
summary="output to contain the surface"/>
</request>
<request name="activate" since="42">
<description summary="activates the window">
Activates this window. This is equivalent to bringing the window to the
foreground. The compositor is free to ignore this request if it deems
the client to be misbehaving.
</description>
</request>
<request name="deactivate" since="42">
<description summary="deactivates the window">
Deactivates this window. This is equivalent to requesting that the
window not be the foreground window. The exact behavior is
compositor-defined. The compositor is free to ignore this request
if it deems the client to be misbehaving.
</description>
</request>
<!-- Version 44 additions -->
<enum name="fullscreen_mode">
<description
summary="Specifies the behavior of the surface in fullscreen.">
Possible windowing system behaviors if this surface were to go
fullscreen.
</description>
<entry
name="plain"
value="0"
summary="user cannot access system UIs using mouse/touches"/>
<entry
name="immersive"
value="1"
summary="user can access system UIs such as the shelf and window frame
by pointing to, or swiping over, the screen edge"/>
</enum>
<request name="set_fullscreen_mode" since="44">
<description summary="Sets the behavior of the surface in fullscreen.">
Suggests how the windowing manager should behave if this surface were
to go fullscreen. Does not make the surface fullscreen.
</description>
<arg name="mode" type="uint" enum="fullscreen_mode"/>
</request>
<!-- Version 46 additions -->
<request name="set_scale_factor" since="46">
<description summary="Allows the client to set the scale factor for the future buffer commits.">
The client has a 32-bit float scale factor that is associated with each
zaura toplevel. This scale factor must be propagated exactly to exo. To
do so we reinterpret_cast into a 32-bit uint and later cast back into a
float. This is because wayland does not support native transport of
floats. As different CPU architectures may use different endian
representations for IEEE 754 floats, this protocol implicitly assumes
that the caller and receiver are the same machine. To avoid redundant
messages, this request needs to only be called once when the zaura
toplevel scale factor changes. This is double buffered state and will be
applied in the next commit.
</description>
<arg name="scale_factor_as_uint" type="uint"/>
</request>
<!-- Version 48 additions-->
<request name="set_snap_primary" since="48">
<description summary="snap the surface to the primary snap position.">
Request that surface is snapped to the left or top if primary layout,
right or bottom otherwise.
</description>/>
<arg name="snap_ratio_as_uint" type="uint"/>
</request>
<request name="set_snap_secondary" since="48">
<description summary="snap the surface to the secondary snap position.">
Request that surface is snapped to the right or bottom if primary
layout, left or top otherwise.
</description>
<arg name="snap_ratio_as_uint" type="uint"/>
</request>
<!-- Version 49 additions-->
<enum name="snap_direction">
<description summary="window snap directions">
Window snap directions.
</description>
<entry name="none" value="0" summary="unsnap the window"/>
<entry name="primary" value="1" summary="snap the window to the left or
top in primary layout, right or bottom in secondary layout"/>
<entry name="secondary" value="2" summary="snap the window to the right
or bottom in primary layout, top or left in secondary layout"/>
</enum>
<request name="intent_to_snap" since="49">
<description summary="client intents to snap the surface.">
Notify (or inform) the server the client's intent to snap the window.
To inform it's no longer willing to snap, send 'none'.
</description>
<arg name="direction" type="uint" enum="snap_direction"/>
</request>
<request name="unset_snap" since="49">
<description summary="Unset the window snap.">
Request that window unsets snapping.
</description>
</request>
<!-- Version 50 additions -->
<event name="configure_raster_scale" since="50">
<description summary="set the raster scale during a configure">
Sets the raster scale of this window. This should be called during a
configure event sequence. To do so we reinterpret_cast into a 32-bit
uint and later cast back into a float. This is because wayland does not
support native transport of floats. As different CPU architectures may
use different endian representations for IEEE 754 floats, this protocol
implicitly assumes that the caller and receiver are the same machine.
</description>
<arg name="scale" type="uint" summary="Raster scale, in float format"/>
</event>
<!-- Version 52 additions -->
<enum name="persistable">
<description summary="Describes whether or not the value is persistable">
Binary enum maps to boolean, describes whether or not a value is
persistable.
</description>
<entry name="not_persistable" value="0" summary="the value is not persistable"/>
<entry name="persistable" value="1" summary="the value is persistable"/>
</enum>
<request name="set_persistable" since="52">
<description summary="Describes if the window is persistable">
Request the persistable status of a window. Sets the persistable status
of the window in its window properties. Should be called before first
commit.
</description>
<arg name="persistable" type="uint" enum="persistable" summary="is the argument persistable"/>
</request>
<!-- Version 53 additions -->
<request name="set_shape" since="53">
<description summary="set the shape of the surface in DP">
Sets the shape of the toplevel window in DP. Passing NULL will reset the
shape of the window.
This should be used only in support of the existing (deprecated) Chrome
Apps SetShape API and not for any other purpose.
</description>
<arg name="region" type="object" interface="wl_region" allow-null="true"/>
</request>
<request name="set_top_inset" since="55">
<description summary="set top inset to the surface">
Sets the top inset to the surface. This represents the header height
and should be non negative.
</description>
<arg name="height" type="int" summary="Top inset of client window. Should be non negative."/>
</request>
<!-- Version 56 additions -->
<enum name="rotate_direction">
<entry name="backward" value="0" />
<entry name="forward" value="1" />
</enum>
<enum name="rotate_restart_state">
<entry name="no_restart" value="0" />
<entry name="restart" value="1" />
</enum>
<event name="rotate_focus" since="56">
<description summary="rotate focus within window">
Rotates focus within the toplevel window. The window must sort its
focusable view into a stable and linearly traversable order. Prior to
rotating focus, the surface should already be activated and have
keyboard focus. If the surface has not been activated or does not have
keyboard focus, the server should first activate and enter keyboard
focus for the window. An example of event order could be:
1. activate surface
2. enter keyboard focus
3. rotate focus
If the window is not activated or does not have keyboard focus, the
client should respond with a "not handled" and not perform any
operation.
To start a new series rotation, the server will set the "restart" arg
to true. If the "restart" arg is set to true, the window should set the
focus on the first UI element for the given direction and not perform
any rotation.
The client should respond with whether the rotation was successful via
the "handled" field in the "ack_rotate_focus" request. The client should
pass on the event serial and direction within the ack message.
</description>
<arg name="serial" type="uint" summary="serial for the rotation event" />
<arg name="direction" type="uint" enum="rotate_direction" summary="the direction for linear traversal" />
<arg name="restart" type="uint" enum="rotate_restart_state" summary="whether or not to restart traversal" />
</event>
<enum name="rotate_handled_state">
<entry name="not_handled" value="0" />
<entry name="handled" value="1" />
</enum>
<request name="ack_rotate_focus" since="56">
<description summary="status of rotate focus event">
If the focus has been successfully rotated between UI elements inside
surface, client replies with 'handled'. If the focus didn't rotate, the
client reply with 'not_handled'. A server may use this to move the focus
to next focusable surface.
Note that a delay in processing in the client could result in stale acks
received by the server.
</description>
<arg name="serial" type="uint" summary="serial for the original; rotation event" />
<arg name="handled" type="uint" enum="rotate_handled_state" summary="whether or not the rotation was successful" />
</request>
<request name="set_can_maximize" since="58">
<description summary="Hint that the toplevel surface can be maximized">
Hints to the window manager that the toplevel surface can be maximized.
</description>
</request>
<request name="unset_can_maximize" since="58">
<description summary="Hint that the toplevel surface should not be maximized">
Hints to the window manager that the toplevel surface should not be
maximized. Note that the window manager might still request the client
to be maximized. In such an event, the client should respect the
window manager's request and maximize. It may unset the maximized state
afterwards.
</description>
</request>
<request name="set_can_fullscreen" since="58">
<description summary="Hint that the toplevel surface can enter fullscreen">
Hints to the window manager that the toplevel surface can enter
fullscreen.
</description>
</request>
<request name="unset_can_fullscreen" since="58">
<description summary="Hint that the toplevel surface should not enter fullscreen">
Hints to the window manager that the toplevel surface should not be
enter fullscreen. Note that the window manager might still request the
client enter fullscreen. In such an event, the client should respect the
window manager's request and enter fullscreen. It may exit fullscreen
afterwards.
</description>
</request>
<!-- Version 59 additions -->
<enum name="float_start_location">
<description
summary="Specifies the location of a surface that just got floated.">
Possible start locations if a surface gets floated.
</description>
<entry
name="bottom_right"
value="0"
summary="On float, surface goes to the bottom right of the work area. This is the default."/>
<entry
name="bottom_left"
value="1"
summary="On float, surface goes to the bottom left of the work area."/>
</enum>
<request name="set_float_to_location" since="59">
<description summary="float the surface on top">
This is a request to place the surface above others.
</description>
<arg name="mode" type="uint" enum="float_start_location"/>
</request>
<!-- Version 60 additions -->
<request name="set_window_corner_radii" since="60">
<description summary="Request to apply rounded corners to the window of the surface.">
The client specifies the radius of each corner to be applied to the
window in DPs (device independent pixels).
The window radius is double buffered, and will be applied at the
time wl_surface.commit of the corresponding wl_surface is called.
Note: Rounded corner radii affects the wl_surface tree, including
subsurfaces. Once this protocol is called, surfaces cannot set
their own rounded corner bounds because rounded window bounds will be
applied to the whole surface tree.
</description>
<arg name="upper_left_radius" type="uint"/>
<arg name="upper_right_radius" type="uint"/>
<arg name="lower_right_radius" type="uint"/>
<arg name="lower_left_radius" type="uint"/>
</request>
<!-- Version 62 additions -->
<enum name="in_overview">
<description summary="Describes whether or not the value is in overview">
Binary enum maps to boolean, describes whether or not a value is in
overview.
</description>
<entry name="not_in_overview" value="0" summary="the value is not in overview"/>
<entry name="in_overview" value="1" summary="the value is in overview"/>
</enum>
<event name="overview_change" since="62">
<description summary="window is in overview">
The window is being shown in overview mode. Note that this is
different than shell overview state, as not all windows will be
part of the overview grid.
</description>
<arg name="in_overview" type="uint" enum="in_overview" summary="in overview or not"/>
</event>
<!-- Version 63 additions -->
<request name="set_shadow_corner_radii" since="63">
<description summary="Request to apply rounded corners to the shadow of the surface.">
The client specifies the radius of each corner to be applied to the shadow
associated with the aura toplevel surface in device independent pixels (DPs).
The shadow radius is double buffered, and will be applied at the
time wl_surface.commit of the corresponding wl_surface is called.
</description>
<arg name="upper_left_radius" type="uint"/>
<arg name="upper_right_radius" type="uint"/>
<arg name="lower_right_radius" type="uint"/>
<arg name="lower_left_radius" type="uint"/>
</request>
</interface>
<interface name="zaura_popup" version="46">
<description summary="aura shell interface to the popup shell">
An interface to the popup shell, which allows the
client to access shell specific functionality.
</description>
<request name="surface_submission_in_pixel_coordinates" since="28">
<description summary="surface will be submitted in pixel coordinates">
Informs the server that when submitting this surface, this client will not
use wl_surface_set_buffer_scale to report the scales, nor will it apply
scale via vp_viewporter. Instead the server should apply an appropriate
scale transform for the submitted buffers to be composited correctly.
</description>
</request>
<request name="set_decoration" since="35">
<description summary="request a decoration for surface">
Clients are allowed to request a particular decoration for a
zaura_toplevel. The server is not required to honor this request. See
decoration_type for available options. Available since M105.
</description>
<arg name="type" type="uint" summary="the new frame type"/>
</request>
<enum name="decoration_type">
<description summary="different decoration types">
Decoration types are used to modify the surface (e.g. drop shadow).
</description>
<entry name="none" value="0" summary="no frame"/>
<entry name="normal" value="1" summary="caption with shadow"/>
<entry name="shadow" value="2" summary="shadow only"/>
</enum>
<request name="set_menu" since="37">
<description summary="set popup type to menu">
Set popup type to menu
</description>
</request>
<!-- Version 38 additions -->
<request name="release" type="destructor" since="38">
<description summary="destroy zaura_popup">
This request destroys the zaura_popup. A client should call destroy when the
role is unmapped from a wl_surface.
See zaura_shell.release for destructor naming.
</description>
</request>
<!-- Version 46 additions -->
<request name="set_scale_factor" since="46">
<description summary="Allows the client to set the scale factor for the future buffer commits.">
The client has a 32-bit float scale factor that is associated with each
zaura popup. This scale factor must be propagated exactly to exo. To
do so we reinterpret_cast into a 32-bit uint and later cast back into a
float. This is because wayland does not support native transport of
floats. As different CPU architectures may use different endian
representations for IEEE 754 floats, this protocol implicitly assumes
that the caller and receiver are the same machine. To avoid redundant
messages, this request needs to only be called once when the zaura
popup's scale factor changes.
</description>
<arg name="scale_factor_as_uint" type="uint"/>
</request>
</interface>
<interface name="zaura_output_manager" version="3">
<description summary="aura shell interface to the output manager">
A global responsible for ensuring clients have a complete view of a given
output's state immediately following the bind of wl_output, and
subsequently as needed.
Clients can expect that all the manager's events for a given wl_output
arrive before the associated wl_output.done event. Clients must bind to
the manager global before any output globals.
</description>
<event name="done" since="1">
<description summary="sent all information about output">
This event is sent after all relevant properties of a
zaura_output_manager for a given wl_output have been sent.
</description>
<arg name="output" type="object" interface="wl_output" />
</event>
<event name="display_id" since="1">
<description summary="advertise the output's display id">
This event describes the 64bit display id assigned to each display by
ChromeOS. The value is opaque and should not be interpreted.
The event is sent when binding to the output object and subsequently as
output state changes.
</description>
<arg name="output" type="object" interface="wl_output" />
<arg name="display_id_hi" type="uint" />
<arg name="display_id_lo" type="uint" />
</event>
<event name="logical_position" since="1">
<description
summary="position of the output within the global compositor space">
The position event describes the location of the wl_output within the
global compositor space.
The event is sent when binding to the output object and subsequently as
output state changes.
</description>
<arg name="output" type="object" interface="wl_output" />
<arg name="x" type="int"
summary="x position within the global compositor space" />
<arg name="y" type="int"
summary="y position within the global compositor space" />
</event>
<event name="logical_size" since="1">
<description summary="size of the output in the global compositor space">
The logical_size event describes the logical size of the output in the
global compositor space.
The event is sent when binding to the output object and subsequently as
output state changes.
</description>
<arg name="output" type="object" interface="wl_output" />
<arg name="width" type="int" summary="width in global compositor space" />
<arg name="height" type="int"
summary="height in global compositor space" />
</event>
<event name="physical_size" since="1">
<description summary="size of the output in pixels">
The physical resolution of the display in pixels. The value should not
include any overscan insets or display rotation, except for any panel
orientation adjustment.
The event is sent when binding to the output object and subsequently as
output state changes.
</description>
<arg name="output" type="object" interface="wl_output" />
<arg name="width" type="int"
summary="width in global compositor space" />
<arg name="height" type="int"
summary="height in global compositor space" />
</event>
<event name="insets" since="1">
<description summary="advertise the work area insets for the output">
This event describes the insets for the output in logical screen
coordinates, from which the work area can be calculated.
The event is sent when binding to the output object and subsequently as
output state changes.
</description>
<arg name="output" type="object" interface="wl_output" />
<arg name="top" type="int" />
<arg name="left" type="int" />
<arg name="bottom" type="int" />
<arg name="right" type="int" />
</event>
<event name="device_scale_factor" since="1">
<description summary="advertise device scale factor for the output">
The scale factor of the output device. We reinterpret_cast the float
scale factor into a 32-bit uint and later cast back into a float. This
is because wayland does not support native transport of floats. As
different CPU architectures may use different endian representations for
IEEE 754 floats, this protocol implicitly assumes that the caller and
receiver are the same machine.
The event is sent when binding to the output object and subsequently as
output state changes.
</description>
<arg name="output" type="object" interface="wl_output" />
<arg name="device_scale_factor" type="uint"
summary="display scale factor, in float format" />
</event>
<event name="logical_transform" since="1">
<description summary="logical transform of the output">
This event describes the logical transform for the output. Whereas
panel transform corresponds to the display's panel rotation, the logical
transform corresponds to the display's logical rotation.
The event is sent when binding to the output object and subsequently as
output state changes.
</description>
<arg name="output" type="object" interface="wl_output" />
<arg name="transform" type="int" enum="wl_output.transform"
summary="transform that maps framebuffer to output" />
</event>
<event name="panel_transform" since="1">
<description summary="panel transform of the output">
This event describes the panel transform for the output, which is the
associated display's panel rotation.
The event is sent when binding to the output object and subsequently as
output state changes.
</description>
<arg name="output" type="object" interface="wl_output" />
<arg name="transform" type="int" enum="wl_output.transform"
summary="transform that maps framebuffer to output" />
</event>
<event name="name" since="1">
<description summary="human-readable name of this output">
The name is a UTF-8 string with no convention defined for its contents.
The event is sent when binding to the output object and subsequently as
output state changes.
</description>
<arg name="output" type="object" interface="wl_output" />
<arg name="name" type="string" summary="output name" />
</event>
<event name="description" since="1">
<description summary="human-readable description of this output">
The description is a UTF-8 string with no convention defined for its
contents.
The event is sent when binding to the output object and subsequently as
output state changes.
</description>
<arg name="output" type="object" interface="wl_output" />
<arg name="description" type="string" summary="output description" />
</event>
<!-- Version 2 additions -->
<event name="activated" since="2">
<description summary="target display for new windows">
Notifies that this output is now active output. It is typically used as
a target when a new window is created without specific bounds.
</description>
<arg name="output" type="object" interface="wl_output" />
</event>
<!-- Version 3 additions -->
<event name="overscan_insets" since="3">
<description summary="advertise the overscan insets for the output">
This event describes the overscan insets for the output in physical
pixels.
The event is sent when binding to the output object and subsequently as
output state changes.
</description>
<arg name="output" type="object" interface="wl_output" />
<arg name="top" type="int" />
<arg name="left" type="int" />
<arg name="bottom" type="int" />
<arg name="right" type="int" />
</event>
</interface>
</protocol>