Lines Matching +full:- +full:- +full:no +full:- +full:commit +full:- +full:id
1 <?xml version="1.0" encoding="UTF-8"?>
5 Copyright © 2008-2011 Kristian Høgsberg
6 Copyright © 2010-2011 Intel Corporation
7 Copyright © 2012-2013 Collabora, Ltd.
24 NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
41 handled in-order and events are delivered in-order, this can
67 The error event is sent out when a fatal (non-recoverable)
94 <description summary="acknowledge object ID deletion">
95 This event is used internally by the object ID management
99 safely reuse the object ID.
101 <arg name="id" type="uint" summary="deleted object ID"/>
124 request. This creates a client-side handle that lets the object
131 Binds a new, client-created object to the server using the
135 <arg name="id" type="new_id" summary="bounded object"/>
156 by name is no longer available. If the client bound to
178 <arg name="callback_data" type="uint" summary="request-specific data for the callback"/>
193 <arg name="id" type="new_id" interface="wl_surface" summary="the new surface"/>
200 <arg name="id" type="new_id" interface="wl_region" summary="the new region"/>
229 <arg name="id" type="new_id" interface="wl_buffer" summary="buffer to create"/>
292 …<entry name="argb8888" value="0" summary="32-bit ARGB format, [31:0] A:R:G:B 8:8:8:8 little endian…
293 …<entry name="xrgb8888" value="1" summary="32-bit RGB format, [31:0] x:R:G:B 8:8:8:8 little endian"…
294 <entry name="c8" value="0x20203843" summary="8-bit color index format, [7:0] C"/>
295 <entry name="rgb332" value="0x38424752" summary="8-bit RGB format, [7:0] R:G:B 3:3:2"/>
296 <entry name="bgr233" value="0x38524742" summary="8-bit BGR format, [7:0] B:G:R 2:3:3"/>
297 …<entry name="xrgb4444" value="0x32315258" summary="16-bit xRGB format, [15:0] x:R:G:B 4:4:4:4 litt…
298 …<entry name="xbgr4444" value="0x32314258" summary="16-bit xBGR format, [15:0] x:B:G:R 4:4:4:4 litt…
299 …<entry name="rgbx4444" value="0x32315852" summary="16-bit RGBx format, [15:0] R:G:B:x 4:4:4:4 litt…
300 …<entry name="bgrx4444" value="0x32315842" summary="16-bit BGRx format, [15:0] B:G:R:x 4:4:4:4 litt…
301 …<entry name="argb4444" value="0x32315241" summary="16-bit ARGB format, [15:0] A:R:G:B 4:4:4:4 litt…
302 …<entry name="abgr4444" value="0x32314241" summary="16-bit ABGR format, [15:0] A:B:G:R 4:4:4:4 litt…
303 …<entry name="rgba4444" value="0x32314152" summary="16-bit RBGA format, [15:0] R:G:B:A 4:4:4:4 litt…
304 …<entry name="bgra4444" value="0x32314142" summary="16-bit BGRA format, [15:0] B:G:R:A 4:4:4:4 litt…
305 …<entry name="xrgb1555" value="0x35315258" summary="16-bit xRGB format, [15:0] x:R:G:B 1:5:5:5 litt…
306 …<entry name="xbgr1555" value="0x35314258" summary="16-bit xBGR 1555 format, [15:0] x:B:G:R 1:5:5:5…
307 …<entry name="rgbx5551" value="0x35315852" summary="16-bit RGBx 5551 format, [15:0] R:G:B:x 5:5:5:1…
308 …<entry name="bgrx5551" value="0x35315842" summary="16-bit BGRx 5551 format, [15:0] B:G:R:x 5:5:5:1…
309 …<entry name="argb1555" value="0x35315241" summary="16-bit ARGB 1555 format, [15:0] A:R:G:B 1:5:5:5…
310 …<entry name="abgr1555" value="0x35314241" summary="16-bit ABGR 1555 format, [15:0] A:B:G:R 1:5:5:5…
311 …<entry name="rgba5551" value="0x35314152" summary="16-bit RGBA 5551 format, [15:0] R:G:B:A 5:5:5:1…
312 …<entry name="bgra5551" value="0x35314142" summary="16-bit BGRA 5551 format, [15:0] B:G:R:A 5:5:5:1…
313 …<entry name="rgb565" value="0x36314752" summary="16-bit RGB 565 format, [15:0] R:G:B 5:6:5 little …
314 …<entry name="bgr565" value="0x36314742" summary="16-bit BGR 565 format, [15:0] B:G:R 5:6:5 little …
315 … <entry name="rgb888" value="0x34324752" summary="24-bit RGB format, [23:0] R:G:B little endian"/>
316 … <entry name="bgr888" value="0x34324742" summary="24-bit BGR format, [23:0] B:G:R little endian"/>
317 …<entry name="xbgr8888" value="0x34324258" summary="32-bit xBGR format, [31:0] x:B:G:R 8:8:8:8 litt…
318 …<entry name="rgbx8888" value="0x34325852" summary="32-bit RGBx format, [31:0] R:G:B:x 8:8:8:8 litt…
319 …<entry name="bgrx8888" value="0x34325842" summary="32-bit BGRx format, [31:0] B:G:R:x 8:8:8:8 litt…
320 …<entry name="abgr8888" value="0x34324241" summary="32-bit ABGR format, [31:0] A:B:G:R 8:8:8:8 litt…
321 …<entry name="rgba8888" value="0x34324152" summary="32-bit RGBA format, [31:0] R:G:B:A 8:8:8:8 litt…
322 …<entry name="bgra8888" value="0x34324142" summary="32-bit BGRA format, [31:0] B:G:R:A 8:8:8:8 litt…
323 …<entry name="xrgb2101010" value="0x30335258" summary="32-bit xRGB format, [31:0] x:R:G:B 2:10:10:1…
324 …<entry name="xbgr2101010" value="0x30334258" summary="32-bit xBGR format, [31:0] x:B:G:R 2:10:10:1…
325 …<entry name="rgbx1010102" value="0x30335852" summary="32-bit RGBx format, [31:0] R:G:B:x 10:10:10:…
326 …<entry name="bgrx1010102" value="0x30335842" summary="32-bit BGRx format, [31:0] B:G:R:x 10:10:10:…
327 …<entry name="argb2101010" value="0x30335241" summary="32-bit ARGB format, [31:0] A:R:G:B 2:10:10:1…
328 …<entry name="abgr2101010" value="0x30334241" summary="32-bit ABGR format, [31:0] A:B:G:R 2:10:10:1…
329 …<entry name="rgba1010102" value="0x30334152" summary="32-bit RGBA format, [31:0] R:G:B:A 10:10:10:…
330 …<entry name="bgra1010102" value="0x30334142" summary="32-bit BGRA format, [31:0] B:G:R:A 10:10:10:…
348 …<entry name="yuv444" value="0x34325559" summary="3 plane YCbCr format, non-subsampled Cb (1) and C…
349 …<entry name="yvu444" value="0x34325659" summary="3 plane YCbCr format, non-subsampled Cr (1) and C…
360 <arg name="id" type="new_id" interface="wl_shm_pool" summary="pool to create"/>
389 For possible side-effects to a surface, see wl_surface.attach.
395 Sent when this wl_buffer is no longer used by the compositor.
400 requested in the same wl_surface.commit that attaches this
415 copy-and-paste and drag-and-drop mechanisms. The offer
440 determine whether the drag-and-drop operation succeeds or not.
443 final result of the drag-and-drop operation. If the end result
444 is that no mime types were accepted, the drag-and-drop operation
450 … <arg name="mime_type" type="string" allow-null="true" summary="mime type accepted by the client"/>
467 both before and after wl_data_device.drop. Drag-and-drop destination
489 <!-- Version 3 additions -->
492 <description summary="the offer will no longer be used">
494 finished the drag-and-drop operation.
502 wl_data_offer.accept or no action was received through
508 <description summary="set the available/preferred drag-and-drop actions">
515 drag-and-drop operation, typically in response to wl_data_device.enter
518 This request determines the final result of the drag-and-drop
519 operation. If the end result is that no action is accepted,
527 While managing an "ask" action, the destination drag-and-drop client
538 This request can only be made on drag-and-drop offers, a protocol error
546 <description summary="notify the source-side available actions">
560 This event can be emitted multiple times during the drag-and-drop
564 This event will no longer be emitted after wl_data_device.drop
565 happened on the drag-and-drop destination, the client must
570 in response to keyboard modifier changes during the drag-and-drop
576 wl_data_device.drop the drag-and-drop destination must honor the
580 especially on "ask" actions, where the drag-and-drop destination
582 at this stage are always the result of inter-client negotiation, the
583 compositor shall no longer be able to induce a different action.
585 Upon "ask" actions, it is expected that the drag-and-drop destination
631 Used for feedback during drag-and-drop.
633 … <arg name="mime_type" type="string" allow-null="true" summary="mime type accepted by the target"/>
648 This data source is no longer valid. There are several reasons why
651 - The data source has been replaced by another data source.
652 - The drag-and-drop operation was performed, but the drop destination
655 - The drag-and-drop operation was performed, but the drop destination
658 - The drag-and-drop operation was performed but didn't happen over a
660 - The compositor cancelled the drag-and-drop operation (e.g. compositor
661 dependent timeouts to avoid stale drag-and-drop transfers).
671 <!-- Version 3 additions -->
674 <description summary="set the available drag-and-drop actions">
685 used in drag-and-drop, so it must be performed before
687 for drag-and-drop will raise a protocol error.
693 <description summary="the drag-and-drop operation physically finished">
699 cancelled the drag-and-drop operation before this event could happen.
707 <description summary="the drag-and-drop operation concluded">
723 This event can be emitted multiple times during the drag-and-drop
729 wl_data_source.dnd_drop_performed if the drag-and-drop operation
734 in response to keyboard modifier changes during the drag-and-drop
754 A wl_data_device provides access to inter-client data transfer
755 mechanisms such as copy-and-paste and drag-and-drop.
763 <description summary="start drag-and-drop operation">
764 This request asks the compositor to start a drag-and-drop
779 the top-left corner of the icon surface is placed at the cursor
782 wl_surface.commit as usual. The icon surface is given the role of
783 a drag-and-drop icon. If the icon surface already has another role,
788 wl_surface is no longer used as the icon surface. When the use
792 …<arg name="source" type="object" interface="wl_data_source" allow-null="true" summary="data source…
794 …<arg name="icon" type="object" interface="wl_surface" allow-null="true" summary="drag-and-drop ico…
805 …<arg name="source" type="object" interface="wl_data_source" allow-null="true" summary="data source…
813 data_device.enter event (for drag-and-drop) or the
819 <arg name="id" type="new_id" interface="wl_data_offer" summary="the new data_offer object"/>
823 <description summary="initiate drag-and-drop session">
824 This event is sent when an active drag-and-drop pointer enters
826 enter time is provided by the x and y arguments, in surface-local
831 <arg name="x" type="fixed" summary="surface-local x coordinate"/>
832 <arg name="y" type="fixed" summary="surface-local y coordinate"/>
833 <arg name="id" type="object" interface="wl_data_offer" allow-null="true"
838 <description summary="end drag-and-drop session">
839 This event is sent when the drag-and-drop pointer leaves the
846 <description summary="drag-and-drop session motion">
847 This event is sent when the drag-and-drop pointer moves within
849 is provided by the x and y arguments, in surface-local
853 <arg name="x" type="fixed" summary="surface-local x coordinate"/>
854 <arg name="y" type="fixed" summary="surface-local y coordinate"/>
858 <description summary="end drag-and-drop session successfully">
859 The event is sent when a drag-and-drop operation is ended
862 The drag-and-drop destination is expected to honor the last action
869 final. The drag-and-drop destination is expected to perform one last
889 <arg name="id" type="object" interface="wl_data_offer" allow-null="true"
893 <!-- Version 2 additions -->
905 provides access to inter-client data transfer mechanisms such as
906 copy-and-paste and drag-and-drop. These mechanisms are tied to
920 <arg name="id" type="new_id" interface="wl_data_source" summary="data source to create"/>
927 <arg name="id" type="new_id" interface="wl_data_device" summary="data device to create"/>
931 <!-- Version 3 additions -->
936 drag-and-drop operation.
941 there is no match. All further checks will effectively happen on
949 - If no modifiers are pressed, the first match (in bit order)
951 - Pressing Shift selects "move", if enabled in the mask.
952 - Pressing Control selects "copy", if enabled in the mask.
954 Behavior beyond that is considered implementation-dependent.
959 <entry name="none" value="0" summary="no action"/>
967 <description summary="create desktop-style surfaces">
969 desktop-style user interfaces.
987 <arg name="id" type="new_id" interface="wl_shell_surface" summary="shell surface to create"/>
993 <description summary="desktop-style metadata interface">
995 implementations that provide a desktop-style user interface.
1017 Start a pointer-driven move of the surface.
1034 <entry name="none" value="0" summary="no edge"/>
1047 Start a pointer-driven resizing of the surface.
1080 parent surface, in surface-local coordinates.
1085 <arg name="x" type="int" summary="surface-local x coordinate"/>
1086 <arg name="y" type="int" summary="surface-local y coordinate"/>
1096 <entry name="default" value="0" summary="no preference, apply default policy"/>
1099 …<entry name="fill" value="3" summary="no upscaling, center on output and add black borders to comp…
1108 output then the compositor will apply its policy - usually
1113 between the output size and the surface size - this is provided
1140 <arg name="output" type="object" interface="wl_output" allow-null="true"
1151 An existing implicit grab will be changed to owner-events mode,
1164 parent surface, in surface-local coordinates.
1169 <arg name="x" type="int" summary="surface-local x coordinate"/>
1170 <arg name="y" type="int" summary="surface-local y coordinate"/>
1180 output then the compositor will apply its policy - usually
1195 <arg name="output" type="object" interface="wl_output" allow-null="true"
1207 The string must be encoded in UTF-8.
1218 file name (or the full path if it is a non-standard location) of
1250 in surface-local coordinates.
1272 in surface-local coordinates, which may differ from the buffer
1280 (wl_data_device.start_drag), a sub-surface
1303 z-order. It is allowed to create a wl_subsurface for the same
1305 a cursor (cursor is a different role than sub-surface, and role
1319 Deletes the surface and invalidates its object ID.
1334 left corner, in surface-local coordinates. In other words, the
1338 Surface contents are double-buffered state, see wl_surface.commit.
1340 The initial surface contents are void; there is no content.
1342 wl_buffer. wl_surface.commit makes the pending wl_buffer the new
1344 calculated from the wl_buffer, as described above. After commit,
1345 there is no pending buffer until the next attach.
1349 any time after the wl_surface.commit request. When the compositor
1363 following wl_surface.commit will remove the surface content.
1365 <arg name="buffer" type="object" interface="wl_buffer" allow-null="true"
1367 <arg name="x" type="int" summary="surface-local x coordinate"/>
1368 <arg name="y" type="int" summary="surface-local y coordinate"/>
1378 Damage is double-buffered state, see wl_surface.commit.
1380 The damage rectangle is specified in surface-local coordinates,
1383 The initial value for pending damage is empty: no damage.
1387 wl_surface.commit assigns pending damage as the current damage,
1395 <arg name="x" type="int" summary="surface-local x coordinate"/>
1396 <arg name="y" type="int" summary="surface-local y coordinate"/>
1408 request to get notified when it is a good time to draw and commit the
1413 The frame request will take effect on the next wl_surface.commit.
1422 to draw and commit after sending the frame callback events to let it
1426 surface is not visible in any way, e.g. the surface is off-screen,
1450 The opaque region is specified in surface-local coordinates.
1455 Opaque region is double-buffered state, see wl_surface.commit.
1458 wl_surface.commit copies the pending region to the current region.
1466 <arg name="region" type="object" interface="wl_region" allow-null="true"
1479 The input region is specified in surface-local coordinates.
1481 Input region is double-buffered state, see wl_surface.commit.
1484 wl_surface.commit copies the pending region to the current region.
1495 <arg name="region" type="object" interface="wl_region" allow-null="true"
1499 <request name="commit">
1500 <description summary="commit pending surface state">
1502 etc.) is double-buffered. Protocol requests modify the pending state,
1503 as opposed to the current state in use by the compositor. A commit
1505 state. After commit, the new pending state is as documented for each
1508 On commit, a pending wl_buffer is applied first, and all other state
1509 second. This means that all coordinates in double-buffered state are
1511 wl_surface.attach itself. If there is no pending wl_buffer, the
1514 All requests that need a commit to become effective are documented
1515 to affect double-buffered state.
1517 Other interfaces may add further double-buffered surface state.
1535 results in it no longer having any part of it within the scanout region
1541 <!-- Version 2 additions -->
1550 Buffer transform is double-buffered state, see wl_surface.commit.
1555 transformation. wl_surface.commit copies the pending buffer
1565 request should be considered on a case-by-case basis.
1579 <!-- Version 3 additions -->
1586 Buffer scale is double-buffered state, see wl_surface.commit.
1591 wl_surface.commit copies the pending buffer scale to the current one.
1611 <!-- Version 4 additions -->
1619 Damage is double-buffered state, see wl_surface.commit.
1624 The initial value for pending damage is empty: no damage.
1628 wl_surface.commit assigns pending damage as the current damage,
1632 This request differs from wl_surface.damage in only one way - it
1633 takes damage in buffer coordinates instead of surface-local
1642 wl_surface.commit time. Therefore, compositors wishing to take both
1645 after receiving the wl_surface.commit.
1647 <arg name="x" type="int" summary="buffer-local x coordinate"/>
1648 <arg name="y" type="int" summary="buffer-local y coordinate"/>
1685 removed, using the wl_pointer.release request. No further pointer
1704 The ID provided will be initialized to the wl_pointer interface
1712 <arg name="id" type="new_id" interface="wl_pointer" summary="seat pointer"/>
1717 The ID provided will be initialized to the wl_keyboard interface
1725 <arg name="id" type="new_id" interface="wl_keyboard" summary="seat keyboard"/>
1730 The ID provided will be initialized to the wl_touch interface
1738 <arg name="id" type="new_id" interface="wl_touch" summary="seat touch interface"/>
1741 <!-- Version 2 additions -->
1752 <!-- Version 5 additions -->
1794 top-left corner is always at (x, y) - (hotspot_x, hotspot_y),
1796 surface-local coordinates.
1801 wl_surface.commit as usual.
1809 wl_surface is no longer used as the cursor. When the use as a
1814 <arg name="surface" type="object" interface="wl_surface" allow-null="true"
1816 <arg name="hotspot_x" type="int" summary="surface-local x coordinate"/>
1817 <arg name="hotspot_y" type="int" summary="surface-local y coordinate"/>
1831 <arg name="surface_x" type="fixed" summary="surface-local x coordinate"/>
1832 <arg name="surface_y" type="fixed" summary="surface-local y coordinate"/>
1837 Notification that this seat's pointer is no longer focused on
1854 <arg name="surface_x" type="fixed" summary="surface-local x coordinate"/>
1855 <arg name="surface_y" type="fixed" summary="surface-local y coordinate"/>
1899 For devices that support movements non-parallel to axes multiple
1911 <arg name="value" type="fixed" summary="length of vector in surface-local coordinate space"/>
1914 <!-- Version 3 additions -->
1926 <!-- Version 5 additions -->
1961 Compositor-specific policies may require the wl_pointer.leave and
1978 finger. One example for this source is button-based scrolling where
2002 for these sources is hardware-specific and implementation-dependent;
2008 axis event sequence, no event is sent.
2055 like two-finger scrolling on touchpads do not have discrete
2059 of -2 is two steps towards the negative direction of this axis.
2084 summary="no keymap; client must understand how to interpret the raw keycode"/>
2092 memory-mapped to provide a keyboard mapping description.
2111 Notification that this seat's keyboard focus is no longer on
2153 <!-- Version 3 additions -->
2159 <!-- Version 4 additions -->
2192 contact point can be identified by the ID of the sequence.
2198 assigned a unique ID. Future events from this touch point reference
2199 this ID. The ID ceases to be valid after a touch up event and may be
2205 <arg name="id" type="int" summary="the unique ID of this touch point"/>
2206 <arg name="x" type="fixed" summary="surface-local x coordinate"/>
2207 <arg name="y" type="fixed" summary="surface-local y coordinate"/>
2212 The touch point has disappeared. No further events will be sent for
2213 this touch point and the touch point's ID is released and may be
2218 <arg name="id" type="int" summary="the unique ID of this touch point"/>
2226 <arg name="id" type="int" summary="the unique ID of this touch point"/>
2227 <arg name="x" type="fixed" summary="surface-local x coordinate"/>
2228 <arg name="y" type="fixed" summary="surface-local y coordinate"/>
2237 A wl_touch.frame terminates at least one event but otherwise no
2247 gesture. No further events are sent to the clients from that
2251 this surface may reuse the touch point ID.
2255 <!-- Version 3 additions -->
2261 <!-- Version 6 additions -->
2277 wl_touch.shape event for this touch ID but both events may occur within
2284 surface-local coordinates. The center of the ellipse is always at the
2291 <arg name="id" type="int" summary="the unique ID of this touch point"/>
2292 … <arg name="major" type="fixed" summary="length of the major axis in surface-local coordinates"/>
2293 … <arg name="minor" type="fixed" summary="length of the minor axis in surface-local coordinates"/>
2310 wl_touch.orientation event for this touch ID but both events may occur
2314 axis to the positive surface y-axis and is normalized to the -180 to
2322 <arg name="id" type="int" summary="the unique ID of this touch point"/>
2323 …ientation" type="fixed" summary="angle between major axis and positive surface y-axis in degrees"/>
2343 <entry name="none" value="1" summary="no geometry"/>
2364 <entry name="normal" value="0" summary="no transform"/>
2365 <entry name="90" value="1" summary="90 degrees counter-clockwise"/>
2366 <entry name="180" value="2" summary="180 degrees counter-clockwise"/>
2367 <entry name="270" value="3" summary="270 degrees counter-clockwise"/>
2369 <entry name="flipped_90" value="5" summary="flip and rotate 90 degrees counter-clockwise"/>
2370 <entry name="flipped_180" value="6" summary="flip and rotate 180 degrees counter-clockwise"/>
2371 <entry name="flipped_270" value="7" summary="flip and rotate 270 degrees counter-clockwise"/>
2431 <!-- Version 2 additions -->
2467 <!-- Version 3 additions -->
2487 Destroy the region. This will invalidate the object ID.
2495 <arg name="x" type="int" summary="region-local x coordinate"/>
2496 <arg name="y" type="int" summary="region-local y coordinate"/>
2505 <arg name="x" type="int" summary="region-local x coordinate"/>
2506 <arg name="y" type="int" summary="region-local y coordinate"/>
2513 <description summary="sub-surface compositing">
2514 The global interface exposing sub-surface compositing capabilities.
2515 A wl_surface, that has sub-surfaces associated, is called the
2516 parent surface. Sub-surfaces can be arbitrarily nested and create
2517 a tree of sub-surfaces.
2519 The root surface in a tree of sub-surfaces is the main
2520 surface. The main surface cannot be a sub-surface, because
2521 sub-surfaces must always have a parent.
2523 A main surface with its sub-surfaces forms a (compound) window.
2528 The aim of sub-surfaces is to offload some of the compositing work
2545 summary="the to-be sub-surface is invalid"/>
2549 <description summary="give a surface the role sub-surface">
2550 Create a sub-surface interface for the given surface, and
2552 plain wl_surface into a sub-surface.
2554 The to-be sub-surface must not already have another role, and it
2558 <arg name="id" type="new_id" interface="wl_subsurface"
2559 summary="the new sub-surface object ID"/>
2561 summary="the surface to be turned into a sub-surface"/>
2568 <description summary="sub-surface interface to a wl_surface">
2570 made a sub-surface. A sub-surface has one parent surface. A
2571 sub-surface's size and position are not limited to that of the parent.
2572 Particularly, a sub-surface is not automatically clipped to its
2575 A sub-surface becomes mapped, when a non-NULL wl_buffer is applied
2577 first is irrelevant. A sub-surface is hidden if the parent becomes
2581 The behaviour of a wl_surface.commit request on a sub-surface
2582 depends on the sub-surface's mode. The possible modes are
2587 wl_surface state directly. A sub-surface is initially in the
2590 Sub-surfaces have also other kind of state, which is managed by
2592 state includes the sub-surface position relative to the parent
2594 the parent and its sub-surfaces (wl_subsurface.place_above and
2596 wl_surface state is applied, regardless of the sub-surface's mode.
2600 since it does not have a parent in the sub-surfaces sense.
2602 Even if a sub-surface is in desynchronized mode, it will behave as
2605 tree of surfaces. This means, that one can set a sub-surface into
2606 synchronized mode, and then assume that all its child and grand-child
2607 sub-surfaces are synchronized, too, without explicitly setting them.
2612 of a sub-surface to the parent surface update, unmap the sub-surface
2614 the sub-surface.
2616 If the parent wl_surface object is destroyed, the sub-surface is
2621 <description summary="remove sub-surface interface">
2622 The sub-surface interface is removed from the wl_surface object
2623 that was turned into a sub-surface with a
2626 a sub-surface. The wl_surface is unmapped.
2636 <description summary="reposition the sub-surface">
2637 This schedules a sub-surface position change.
2638 The sub-surface will be moved so that its origin (top left
2649 the commit of the parent surface, the position of a new request always
2659 <description summary="restack the sub-surface">
2660 This sub-surface is taken from the stack, and put back just
2661 above the reference surface, changing the z-order of the sub-surfaces.
2663 parent surface. Using any other surface, including this sub-surface,
2666 The z-order is double-buffered. Requests are handled in order and
2673 A new sub-surface is initially added as the top-most in the stack
2681 <description summary="restack the sub-surface">
2682 The sub-surface is placed just below the reference surface.
2690 <description summary="set sub-surface to synchronized mode">
2691 Change the commit behaviour of the sub-surface to synchronized
2694 In synchronized mode, wl_surface.commit on a sub-surface will
2697 The cached state is applied to the sub-surface immediately after
2699 updates of the parent and all its synchronized sub-surfaces.
2701 parent surface commits do not (re-)apply old state.
2708 <description summary="set sub-surface to desynchronized mode">
2709 Change the commit behaviour of the sub-surface to desynchronized
2712 In desynchronized mode, wl_surface.commit on a sub-surface will
2714 normally with a wl_surface. Calling wl_surface.commit on the
2715 parent surface has no effect on the sub-surface's wl_surface
2716 state. This mode allows a sub-surface to be updated on its own.
2718 If cached state exists when wl_surface.commit is called in
2722 Note: even if a sub-surface is set to desynchronized, a parent
2723 sub-surface may override it to behave as synchronized. For details,