wayland: Keep protocol XML files in-tree.
authorRyan C. Gordon <icculus@icculus.org>
Mon, 25 Jun 2018 09:37:25 -0700
changeset 120351a7dec71e8e0
parent 12034 b3ae0dc577fd
child 12036 e001d73657b3
wayland: Keep protocol XML files in-tree.

Now you don't need the latest Wayland installed to build with
newer protocols supported, as they'll build correctly; even if
your system can't use them, we can make intelligent decisions
at runtime about what's available on the current machine anyhow.

This also simplifies some logic and possible failure cases in
the configure and CMake scripts.

Fixes Bugzilla #4207.
Makefile.in
cmake/sdlchecks.cmake
configure
configure.in
wayland-protocols/pointer-constraints-unstable-v1.xml
wayland-protocols/relative-pointer-unstable-v1.xml
wayland-protocols/wayland.xml
wayland-protocols/xdg-shell-unstable-v6.xml
wayland-protocols/xdg-shell.xml
     1.1 --- a/Makefile.in	Mon Jun 25 01:57:28 2018 -0400
     1.2 +++ b/Makefile.in	Mon Jun 25 09:37:25 2018 -0700
     1.3 @@ -44,7 +44,7 @@
     1.4  
     1.5  WAYLAND_SCANNER = @WAYLAND_SCANNER@
     1.6  
     1.7 -SRC_DIST = *.txt acinclude Android.mk autogen.sh android-project build-scripts cmake cmake_uninstall.cmake.in configure configure.in debian docs include Makefile.* sdl2-config.cmake.in sdl2-config.in sdl2.m4 sdl2.pc.in SDL2.spec.in SDL2Config.cmake src test VisualC.html VisualC VisualC-WinRT Xcode Xcode-iOS
     1.8 +SRC_DIST = *.txt acinclude Android.mk autogen.sh android-project build-scripts cmake cmake_uninstall.cmake.in configure configure.in debian docs include Makefile.* sdl2-config.cmake.in sdl2-config.in sdl2.m4 sdl2.pc.in SDL2.spec.in SDL2Config.cmake src test VisualC.html VisualC VisualC-WinRT Xcode Xcode-iOS wayland-protocols
     1.9  GEN_DIST = SDL2.spec
    1.10  
    1.11  ifneq ($V,1)
     2.1 --- a/cmake/sdlchecks.cmake	Mon Jun 25 01:57:28 2018 -0400
     2.2 +++ b/cmake/sdlchecks.cmake	Mon Jun 25 09:37:25 2018 -0700
     2.3 @@ -635,35 +635,6 @@
     2.4    if(VIDEO_WAYLAND)
     2.5      pkg_check_modules(WAYLAND wayland-client wayland-scanner wayland-protocols wayland-egl wayland-cursor egl xkbcommon)
     2.6  
     2.7 -    # We have to generate some protocol interface code for some various Wayland features.
     2.8 -    if(WAYLAND_FOUND)
     2.9 -      execute_process(
    2.10 -        COMMAND ${PKG_CONFIG_EXECUTABLE} --variable=pkgdatadir wayland-client
    2.11 -        WORKING_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}"
    2.12 -        RESULT_VARIABLE WAYLAND_CORE_PROTOCOL_DIR_RC
    2.13 -        OUTPUT_VARIABLE WAYLAND_CORE_PROTOCOL_DIR
    2.14 -        ERROR_QUIET
    2.15 -        OUTPUT_STRIP_TRAILING_WHITESPACE
    2.16 -      )
    2.17 -      if(NOT WAYLAND_CORE_PROTOCOL_DIR_RC EQUAL 0)
    2.18 -        set(WAYLAND_FOUND FALSE)
    2.19 -      endif()
    2.20 -    endif()
    2.21 -
    2.22 -    if(WAYLAND_FOUND)
    2.23 -      execute_process(
    2.24 -        COMMAND ${PKG_CONFIG_EXECUTABLE} --variable=pkgdatadir wayland-protocols
    2.25 -        WORKING_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}"
    2.26 -        RESULT_VARIABLE WAYLAND_PROTOCOLS_DIR_RC
    2.27 -        OUTPUT_VARIABLE WAYLAND_PROTOCOLS_DIR
    2.28 -        ERROR_QUIET
    2.29 -        OUTPUT_STRIP_TRAILING_WHITESPACE
    2.30 -      )
    2.31 -      if(NOT WAYLAND_PROTOCOLS_DIR_RC EQUAL 0)
    2.32 -        set(WAYLAND_FOUND FALSE)
    2.33 -      endif()
    2.34 -    endif()
    2.35 -
    2.36      if(WAYLAND_FOUND)
    2.37        execute_process(
    2.38          COMMAND ${PKG_CONFIG_EXECUTABLE} --variable=wayland_scanner wayland-scanner
    2.39 @@ -695,11 +666,10 @@
    2.40        file(MAKE_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}/wayland-generated-protocols")
    2.41        include_directories("${CMAKE_CURRENT_BINARY_DIR}/wayland-generated-protocols")
    2.42  
    2.43 -      WaylandProtocolGen("${WAYLAND_SCANNER}" "${WAYLAND_CORE_PROTOCOL_DIR}/wayland.xml" "wayland")
    2.44 -
    2.45 -      foreach(_PROTL relative-pointer-unstable-v1 pointer-constraints-unstable-v1 xdg-shell-unstable-v6)
    2.46 -        string(REGEX REPLACE "\\-unstable\\-.*$" "" PROTSUBDIR ${_PROTL})
    2.47 -        WaylandProtocolGen("${WAYLAND_SCANNER}" "${WAYLAND_PROTOCOLS_DIR}/unstable/${PROTSUBDIR}/${_PROTL}.xml" "${_PROTL}")
    2.48 +      file(GLOB WAYLAND_PROTOCOLS_XML RELATIVE "${SDL2_SOURCE_DIR}/wayland-protocols/" "${SDL2_SOURCE_DIR}/wayland-protocols/*.xml")
    2.49 +      foreach(_XML ${WAYLAND_PROTOCOLS_XML})
    2.50 +        string(REGEX REPLACE "\\.xml$" "" _PROTL "${_XML}")
    2.51 +        WaylandProtocolGen("${WAYLAND_SCANNER}" "${SDL2_SOURCE_DIR}/wayland-protocols/${_XML}" "${_PROTL}")
    2.52        endforeach()
    2.53  
    2.54        if(VIDEO_WAYLAND_QT_TOUCH)
     3.1 --- a/configure	Mon Jun 25 01:57:28 2018 -0400
     3.2 +++ b/configure	Mon Jun 25 09:37:25 2018 -0700
     3.3 @@ -19209,8 +19209,6 @@
     3.4                  WAYLAND_CFLAGS=`$PKG_CONFIG --cflags wayland-client wayland-egl wayland-cursor xkbcommon`
     3.5                  WAYLAND_LIBS=`$PKG_CONFIG --libs wayland-client wayland-egl wayland-cursor xkbcommon`
     3.6                  WAYLAND_SCANNER=`$PKG_CONFIG --variable=wayland_scanner wayland-scanner`
     3.7 -                WAYLAND_CORE_PROTOCOL_DIR=`$PKG_CONFIG --variable=pkgdatadir wayland-client`
     3.8 -                WAYLAND_PROTOCOLS_DIR=`$PKG_CONFIG --variable=pkgdatadir wayland-protocols`
     3.9                  video_wayland=yes
    3.10              fi
    3.11          fi
    3.12 @@ -19227,9 +19225,6 @@
    3.13  
    3.14              fi
    3.15  
    3.16 -            WAYLAND_PROTOCOLS_UNSTABLE="relative-pointer-unstable-v1 pointer-constraints-unstable-v1 xdg-shell-unstable-v6"
    3.17 -            WAYLAND_PROTOCOLS_STABLE="xdg-shell"
    3.18 -
    3.19              SOURCES="$SOURCES $srcdir/src/video/wayland/*.c"
    3.20              EXTRA_CFLAGS="$EXTRA_CFLAGS $WAYLAND_CFLAGS -I\$(gen)"
    3.21              # Check whether --enable-wayland-shared was given.
    3.22 @@ -24711,74 +24706,25 @@
    3.23  SDLTEST_SOURCES="$srcdir/src/test/*.c"
    3.24  
    3.25  if test x$video_wayland = xyes; then
    3.26 -    WAYLAND_CORE_PROTOCOL_SOURCE='$(gen)/wayland-protocol.c'
    3.27 -    WAYLAND_CORE_PROTOCOL_HEADER='$(gen)/wayland-client-protocol.h'
    3.28 -    WAYLAND_PROTOCOLS_SOURCES=`echo $WAYLAND_PROTOCOLS_UNSTABLE $WAYLAND_PROTOCOLS_STABLE |\
    3.29 -        sed 's,[^ ]\+,\\$(gen)/&-protocol.c,g'`
    3.30 -    WAYLAND_PROTOCOLS_HEADERS=`echo $WAYLAND_PROTOCOLS_UNSTABLE $WAYLAND_PROTOCOLS_STABLE |\
    3.31 -        sed 's,[^ ]\+,\\$(gen)/&-client-protocol.h,g'`
    3.32 -    GEN_SOURCES="$GEN_SOURCES $WAYLAND_CORE_PROTOCOL_SOURCE $WAYLAND_PROTOCOLS_SOURCES"
    3.33 -    GEN_HEADERS="$GEN_HEADERS $WAYLAND_CORE_PROTOCOL_HEADER $WAYLAND_PROTOCOLS_HEADERS"
    3.34 -
    3.35 -    WAYLAND_CORE_PROTOCOL_SOURCE_DEPENDS="
    3.36 -$WAYLAND_CORE_PROTOCOL_SOURCE: $WAYLAND_CORE_PROTOCOL_DIR/wayland.xml
    3.37 -	@\$(SHELL) \$(auxdir)/mkinstalldirs \$(gen)
    3.38 -	\$(RUN_CMD_GEN)\$(WAYLAND_SCANNER) code \$< \$@"
    3.39 -
    3.40 -    WAYLAND_CORE_PROTOCOL_HEADER_DEPENDS="
    3.41 -$WAYLAND_CORE_PROTOCOL_HEADER: $WAYLAND_CORE_PROTOCOL_DIR/wayland.xml
    3.42 -	@\$(SHELL) \$(auxdir)/mkinstalldirs \$(gen)
    3.43 -	\$(RUN_CMD_GEN)\$(WAYLAND_SCANNER) client-header \$< \$@"
    3.44 -
    3.45 -    WAYLAND_CORE_PROTOCOL_OBJECT="
    3.46 -\$(objects)/`echo $WAYLAND_CORE_PROTOCOL_SOURCE | sed 's/\$(gen)\/\(.*\).c$/\1.lo/'`: $WAYLAND_CORE_PROTOCOL_SOURCE
    3.47 -	\$(RUN_CMD_CC)\$(LIBTOOL) --tag=CC --mode=compile \$(CC) \$(CFLAGS) \$(EXTRA_CFLAGS) $DEPENDENCY_TRACKING_OPTIONS -c \$< -o \$@"
    3.48 -
    3.49 -    WAYLAND_PROTOCOLS_CLIENT_HEADER_UNSTABLE_DEPENDS=`for p in $WAYLAND_PROTOCOLS_UNSTABLE;\
    3.50 -        do echo ; echo \$p | sed\
    3.51 -        "s,^\\([a-z\\-]\\+\\)-unstable-\\(v[0-9]\+\\)\$,\\$(gen)/&-client-protocol.h: $WAYLAND_PROTOCOLS_DIR/unstable/\1/&.xml\\\\
    3.52 -	@\\$(SHELL) \\$(auxdir)/mkinstalldirs \\$(gen)\\\\
    3.53 -	\\$(RUN_CMD_GEN)\\$(WAYLAND_SCANNER) client-header \\$< \\$@," ; done`
    3.54 -
    3.55 -    WAYLAND_PROTOCOLS_CLIENT_HEADER_STABLE_DEPENDS=`for p in $WAYLAND_PROTOCOLS_STABLE;\
    3.56 -        do echo ; echo \$p | sed\
    3.57 -        "s,^\\([a-z\\-]\\+\\)\$,\\$(gen)/&-client-protocol.h: $WAYLAND_PROTOCOLS_DIR/stable/\1/&.xml\\\\
    3.58 -	@\\$(SHELL) \\$(auxdir)/mkinstalldirs \\$(gen)\\\\
    3.59 -	\\$(RUN_CMD_GEN)\\$(WAYLAND_SCANNER) client-header \\$< \\$@," ; done`
    3.60 -
    3.61 -    WAYLAND_PROTOCOLS_CODE_UNSTABLE_DEPENDS=`for p in $WAYLAND_PROTOCOLS_UNSTABLE;\
    3.62 -        do echo ; echo \$p | sed\
    3.63 -        "s,^\\([a-z\\-]\\+\\)-unstable-\\(v[0-9]\+\\)\$,\\$(gen)/&-protocol.c: $WAYLAND_PROTOCOLS_DIR/unstable/\1/&.xml\\\\
    3.64 -	@\\$(SHELL) \\$(auxdir)/mkinstalldirs \\$(gen)\\\\
    3.65 -	\\$(RUN_CMD_GEN)\\$(WAYLAND_SCANNER) code \\$< \\$@," ; done`
    3.66 -
    3.67 -    WAYLAND_PROTOCOLS_CODE_STABLE_DEPENDS=`for p in $WAYLAND_PROTOCOLS_STABLE;\
    3.68 -        do echo ; echo \$p | sed\
    3.69 -        "s,^\\([a-z\\-]\\+\\)\$,\\$(gen)/&-protocol.c: $WAYLAND_PROTOCOLS_DIR/stable/\1/&.xml\\\\
    3.70 -	@\\$(SHELL) \\$(auxdir)/mkinstalldirs \\$(gen)\\\\
    3.71 -	\\$(RUN_CMD_GEN)\\$(WAYLAND_SCANNER) code \\$< \\$@," ; done`
    3.72 -
    3.73 -    WAYLAND_PROTOCOLS_OBJECTS_UNSTABLE=`for p in $WAYLAND_PROTOCOLS_UNSTABLE;\
    3.74 -        do echo ; echo \$p | sed\
    3.75 -        "s,^\\([a-z\\-]\\+\\)-unstable-\\(v[0-9]\+\\)\$,\\\$(objects)/&-protocol.lo: \\$(gen)/&-protocol.c \\$(gen)/&-client-protocol.h\\\\
    3.76 -	\\$(RUN_CMD_CC)\\$(LIBTOOL) --tag=CC --mode=compile \\$(CC) \\$(CFLAGS) \\$(EXTRA_CFLAGS) $DEPENDENCY_TRACKING_OPTIONS -c \\$< -o \\$@," ; done`
    3.77 -
    3.78 -    WAYLAND_PROTOCOLS_OBJECTS_STABLE=`for p in $WAYLAND_PROTOCOLS_STABLE;\
    3.79 -        do echo ; echo \$p | sed\
    3.80 -        "s,^\\([a-z\\-]\\+\\)\$,\\\$(objects)/&-protocol.lo: \\$(gen)/&-protocol.c \\$(gen)/&-client-protocol.h\\\\
    3.81 -	\\$(RUN_CMD_CC)\\$(LIBTOOL) --tag=CC --mode=compile \\$(CC) \\$(CFLAGS) \\$(EXTRA_CFLAGS) $DEPENDENCY_TRACKING_OPTIONS -c \\$< -o \\$@," ; done`
    3.82 -
    3.83 -    WAYLAND_PROTOCOLS_DEPENDS="
    3.84 -$WAYLAND_CORE_PROTOCOL_SOURCE_DEPENDS
    3.85 -$WAYLAND_CORE_PROTOCOL_HEADER_DEPENDS
    3.86 -$WAYLAND_CORE_PROTOCOL_OBJECT
    3.87 -$WAYLAND_PROTOCOLS_CLIENT_HEADER_UNSTABLE_DEPENDS
    3.88 -$WAYLAND_PROTOCOLS_CLIENT_HEADER_STABLE_DEPENDS
    3.89 -$WAYLAND_PROTOCOLS_CODE_UNSTABLE_DEPENDS
    3.90 -$WAYLAND_PROTOCOLS_CODE_STABLE_DEPENDS
    3.91 -$WAYLAND_PROTOCOLS_OBJECTS_UNSTABLE
    3.92 -$WAYLAND_PROTOCOLS_OBJECTS_STABLE
    3.93 -"
    3.94 +    WAYLAND_PROTOCOLS=`cd $srcdir/wayland-protocols ; for p in *.xml ; do echo -n "\$p" |sed 's,\\.xml\$, ,g' ; done`
    3.95 +    WAYLAND_PROTOCOLS_SOURCES=`for p in $WAYLAND_PROTOCOLS ; do echo -n "\\$(gen)/\$p-protocol.c " ; done`
    3.96 +    WAYLAND_PROTOCOLS_HEADERS=`for p in $WAYLAND_PROTOCOLS ; do echo -n "\\$(gen)/\$p-client-protocol.h " ; done`
    3.97 +    GEN_SOURCES="$GEN_SOURCES $WAYLAND_PROTOCOLS_SOURCES"
    3.98 +    GEN_HEADERS="$GEN_HEADERS $WAYLAND_PROTOCOLS_HEADERS"
    3.99 +
   3.100 +    WAYLAND_PROTOCOLS_DEPENDS=`for p in $WAYLAND_PROTOCOLS ; do\
   3.101 +        echo ;\
   3.102 +        echo "\\$(gen)/\$p-client-protocol.h: \\$(srcdir)/wayland-protocols/\$p.xml" ;\
   3.103 +        echo "	@\\$(SHELL) \\$(auxdir)/mkinstalldirs \\$(gen)" ;\
   3.104 +        echo "	\\$(RUN_CMD_GEN)\\$(WAYLAND_SCANNER) client-header \\$< \\$@" ;\
   3.105 +        echo ;\
   3.106 +        echo "\\$(gen)/\$p-protocol.c: \\$(srcdir)/wayland-protocols/\$p.xml" ;\
   3.107 +        echo "	@\\$(SHELL) \\$(auxdir)/mkinstalldirs \\$(gen)" ;\
   3.108 +        echo "	\\$(RUN_CMD_GEN)\\$(WAYLAND_SCANNER) code \\$< \\$@" ;\
   3.109 +        echo ;\
   3.110 +        echo "\\$(objects)/\$p-protocol.lo: \\$(gen)/\$p-protocol.c \\$(gen)/\$p-client-protocol.h" ;\
   3.111 +        echo "	\\$(RUN_CMD_CC)\\$(LIBTOOL) --tag=CC --mode=compile \\$(CC) \\$(CFLAGS) \\$(EXTRA_CFLAGS) $DEPENDENCY_TRACKING_OPTIONS -c \\$< -o \\$@" ;\
   3.112 +        done`
   3.113  fi
   3.114  
   3.115  OBJECTS=`echo $SOURCES`
     4.1 --- a/configure.in	Mon Jun 25 01:57:28 2018 -0400
     4.2 +++ b/configure.in	Mon Jun 25 09:37:25 2018 -0700
     4.3 @@ -1403,8 +1403,6 @@
     4.4                  WAYLAND_CFLAGS=`$PKG_CONFIG --cflags wayland-client wayland-egl wayland-cursor xkbcommon`
     4.5                  WAYLAND_LIBS=`$PKG_CONFIG --libs wayland-client wayland-egl wayland-cursor xkbcommon`
     4.6                  WAYLAND_SCANNER=`$PKG_CONFIG --variable=wayland_scanner wayland-scanner`
     4.7 -                WAYLAND_CORE_PROTOCOL_DIR=`$PKG_CONFIG --variable=pkgdatadir wayland-client`
     4.8 -                WAYLAND_PROTOCOLS_DIR=`$PKG_CONFIG --variable=pkgdatadir wayland-protocols`
     4.9                  video_wayland=yes
    4.10              fi
    4.11          fi
    4.12 @@ -1416,9 +1414,6 @@
    4.13                  AC_DEFINE(SDL_VIDEO_DRIVER_WAYLAND_QT_TOUCH, 1, [ ])
    4.14              fi
    4.15  
    4.16 -            WAYLAND_PROTOCOLS_UNSTABLE="relative-pointer-unstable-v1 pointer-constraints-unstable-v1 xdg-shell-unstable-v6"
    4.17 -            WAYLAND_PROTOCOLS_STABLE="xdg-shell"
    4.18 -
    4.19              SOURCES="$SOURCES $srcdir/src/video/wayland/*.c"
    4.20              EXTRA_CFLAGS="$EXTRA_CFLAGS $WAYLAND_CFLAGS -I\$(gen)"
    4.21              AC_ARG_ENABLE(wayland-shared,
    4.22 @@ -3978,74 +3973,25 @@
    4.23  SDLTEST_SOURCES="$srcdir/src/test/*.c"
    4.24  
    4.25  if test x$video_wayland = xyes; then
    4.26 -    WAYLAND_CORE_PROTOCOL_SOURCE='$(gen)/wayland-protocol.c'
    4.27 -    WAYLAND_CORE_PROTOCOL_HEADER='$(gen)/wayland-client-protocol.h'
    4.28 -    WAYLAND_PROTOCOLS_SOURCES=`echo $WAYLAND_PROTOCOLS_UNSTABLE $WAYLAND_PROTOCOLS_STABLE |\
    4.29 -        sed 's,[[^ ]]\+,\\$(gen)/&-protocol.c,g'`
    4.30 -    WAYLAND_PROTOCOLS_HEADERS=`echo $WAYLAND_PROTOCOLS_UNSTABLE $WAYLAND_PROTOCOLS_STABLE |\
    4.31 -        sed 's,[[^ ]]\+,\\$(gen)/&-client-protocol.h,g'`
    4.32 -    GEN_SOURCES="$GEN_SOURCES $WAYLAND_CORE_PROTOCOL_SOURCE $WAYLAND_PROTOCOLS_SOURCES"
    4.33 -    GEN_HEADERS="$GEN_HEADERS $WAYLAND_CORE_PROTOCOL_HEADER $WAYLAND_PROTOCOLS_HEADERS"
    4.34 -
    4.35 -    WAYLAND_CORE_PROTOCOL_SOURCE_DEPENDS="
    4.36 -$WAYLAND_CORE_PROTOCOL_SOURCE: $WAYLAND_CORE_PROTOCOL_DIR/wayland.xml
    4.37 -	@\$(SHELL) \$(auxdir)/mkinstalldirs \$(gen)
    4.38 -	\$(RUN_CMD_GEN)\$(WAYLAND_SCANNER) code \$< \$@"
    4.39 -
    4.40 -    WAYLAND_CORE_PROTOCOL_HEADER_DEPENDS="
    4.41 -$WAYLAND_CORE_PROTOCOL_HEADER: $WAYLAND_CORE_PROTOCOL_DIR/wayland.xml
    4.42 -	@\$(SHELL) \$(auxdir)/mkinstalldirs \$(gen)
    4.43 -	\$(RUN_CMD_GEN)\$(WAYLAND_SCANNER) client-header \$< \$@"
    4.44 -
    4.45 -    WAYLAND_CORE_PROTOCOL_OBJECT="
    4.46 -\$(objects)/`echo $WAYLAND_CORE_PROTOCOL_SOURCE | sed 's/\$(gen)\/\(.*\).c$/\1.lo/'`: $WAYLAND_CORE_PROTOCOL_SOURCE
    4.47 -	\$(RUN_CMD_CC)\$(LIBTOOL) --tag=CC --mode=compile \$(CC) \$(CFLAGS) \$(EXTRA_CFLAGS) $DEPENDENCY_TRACKING_OPTIONS -c \$< -o \$@"
    4.48 -
    4.49 -    WAYLAND_PROTOCOLS_CLIENT_HEADER_UNSTABLE_DEPENDS=`for p in $WAYLAND_PROTOCOLS_UNSTABLE;\
    4.50 -        do echo ; echo \$p | sed\
    4.51 -        "s,^\\([[a-z\\-]]\\+\\)-unstable-\\(v[[0-9]]\+\\)\$,\\$(gen)/&-client-protocol.h: $WAYLAND_PROTOCOLS_DIR/unstable/\1/&.xml\\\\
    4.52 -	@\\$(SHELL) \\$(auxdir)/mkinstalldirs \\$(gen)\\\\
    4.53 -	\\$(RUN_CMD_GEN)\\$(WAYLAND_SCANNER) client-header \\$< \\$@," ; done`
    4.54 -
    4.55 -    WAYLAND_PROTOCOLS_CLIENT_HEADER_STABLE_DEPENDS=`for p in $WAYLAND_PROTOCOLS_STABLE;\
    4.56 -        do echo ; echo \$p | sed\
    4.57 -        "s,^\\([[a-z\\-]]\\+\\)\$,\\$(gen)/&-client-protocol.h: $WAYLAND_PROTOCOLS_DIR/stable/\1/&.xml\\\\
    4.58 -	@\\$(SHELL) \\$(auxdir)/mkinstalldirs \\$(gen)\\\\
    4.59 -	\\$(RUN_CMD_GEN)\\$(WAYLAND_SCANNER) client-header \\$< \\$@," ; done`
    4.60 -
    4.61 -    WAYLAND_PROTOCOLS_CODE_UNSTABLE_DEPENDS=`for p in $WAYLAND_PROTOCOLS_UNSTABLE;\
    4.62 -        do echo ; echo \$p | sed\
    4.63 -        "s,^\\([[a-z\\-]]\\+\\)-unstable-\\(v[[0-9]]\+\\)\$,\\$(gen)/&-protocol.c: $WAYLAND_PROTOCOLS_DIR/unstable/\1/&.xml\\\\
    4.64 -	@\\$(SHELL) \\$(auxdir)/mkinstalldirs \\$(gen)\\\\
    4.65 -	\\$(RUN_CMD_GEN)\\$(WAYLAND_SCANNER) code \\$< \\$@," ; done`
    4.66 -
    4.67 -    WAYLAND_PROTOCOLS_CODE_STABLE_DEPENDS=`for p in $WAYLAND_PROTOCOLS_STABLE;\
    4.68 -        do echo ; echo \$p | sed\
    4.69 -        "s,^\\([[a-z\\-]]\\+\\)\$,\\$(gen)/&-protocol.c: $WAYLAND_PROTOCOLS_DIR/stable/\1/&.xml\\\\
    4.70 -	@\\$(SHELL) \\$(auxdir)/mkinstalldirs \\$(gen)\\\\
    4.71 -	\\$(RUN_CMD_GEN)\\$(WAYLAND_SCANNER) code \\$< \\$@," ; done`
    4.72 -
    4.73 -    WAYLAND_PROTOCOLS_OBJECTS_UNSTABLE=`for p in $WAYLAND_PROTOCOLS_UNSTABLE;\
    4.74 -        do echo ; echo \$p | sed\
    4.75 -        "s,^\\([[a-z\\-]]\\+\\)-unstable-\\(v[[0-9]]\+\\)\$,\\\$(objects)/&-protocol.lo: \\$(gen)/&-protocol.c \\$(gen)/&-client-protocol.h\\\\
    4.76 -	\\$(RUN_CMD_CC)\\$(LIBTOOL) --tag=CC --mode=compile \\$(CC) \\$(CFLAGS) \\$(EXTRA_CFLAGS) $DEPENDENCY_TRACKING_OPTIONS -c \\$< -o \\$@," ; done`
    4.77 -
    4.78 -    WAYLAND_PROTOCOLS_OBJECTS_STABLE=`for p in $WAYLAND_PROTOCOLS_STABLE;\
    4.79 -        do echo ; echo \$p | sed\
    4.80 -        "s,^\\([[a-z\\-]]\\+\\)\$,\\\$(objects)/&-protocol.lo: \\$(gen)/&-protocol.c \\$(gen)/&-client-protocol.h\\\\
    4.81 -	\\$(RUN_CMD_CC)\\$(LIBTOOL) --tag=CC --mode=compile \\$(CC) \\$(CFLAGS) \\$(EXTRA_CFLAGS) $DEPENDENCY_TRACKING_OPTIONS -c \\$< -o \\$@," ; done`
    4.82 -
    4.83 -    WAYLAND_PROTOCOLS_DEPENDS="
    4.84 -$WAYLAND_CORE_PROTOCOL_SOURCE_DEPENDS
    4.85 -$WAYLAND_CORE_PROTOCOL_HEADER_DEPENDS
    4.86 -$WAYLAND_CORE_PROTOCOL_OBJECT
    4.87 -$WAYLAND_PROTOCOLS_CLIENT_HEADER_UNSTABLE_DEPENDS
    4.88 -$WAYLAND_PROTOCOLS_CLIENT_HEADER_STABLE_DEPENDS
    4.89 -$WAYLAND_PROTOCOLS_CODE_UNSTABLE_DEPENDS
    4.90 -$WAYLAND_PROTOCOLS_CODE_STABLE_DEPENDS
    4.91 -$WAYLAND_PROTOCOLS_OBJECTS_UNSTABLE
    4.92 -$WAYLAND_PROTOCOLS_OBJECTS_STABLE
    4.93 -"
    4.94 +    WAYLAND_PROTOCOLS=`cd $srcdir/wayland-protocols ; for p in *.xml ; do echo -n "\$p" |sed 's,\\.xml\$, ,g' ; done`
    4.95 +    WAYLAND_PROTOCOLS_SOURCES=`for p in $WAYLAND_PROTOCOLS ; do echo -n "\\$(gen)/\$p-protocol.c " ; done`
    4.96 +    WAYLAND_PROTOCOLS_HEADERS=`for p in $WAYLAND_PROTOCOLS ; do echo -n "\\$(gen)/\$p-client-protocol.h " ; done`
    4.97 +    GEN_SOURCES="$GEN_SOURCES $WAYLAND_PROTOCOLS_SOURCES"
    4.98 +    GEN_HEADERS="$GEN_HEADERS $WAYLAND_PROTOCOLS_HEADERS"
    4.99 +
   4.100 +    WAYLAND_PROTOCOLS_DEPENDS=`for p in $WAYLAND_PROTOCOLS ; do\
   4.101 +        echo ;\
   4.102 +        echo "\\$(gen)/\$p-client-protocol.h: \\$(srcdir)/wayland-protocols/\$p.xml" ;\
   4.103 +        echo "	@\\$(SHELL) \\$(auxdir)/mkinstalldirs \\$(gen)" ;\
   4.104 +        echo "	\\$(RUN_CMD_GEN)\\$(WAYLAND_SCANNER) client-header \\$< \\$@" ;\
   4.105 +        echo ;\
   4.106 +        echo "\\$(gen)/\$p-protocol.c: \\$(srcdir)/wayland-protocols/\$p.xml" ;\
   4.107 +        echo "	@\\$(SHELL) \\$(auxdir)/mkinstalldirs \\$(gen)" ;\
   4.108 +        echo "	\\$(RUN_CMD_GEN)\\$(WAYLAND_SCANNER) code \\$< \\$@" ;\
   4.109 +        echo ;\
   4.110 +        echo "\\$(objects)/\$p-protocol.lo: \\$(gen)/\$p-protocol.c \\$(gen)/\$p-client-protocol.h" ;\
   4.111 +        echo "	\\$(RUN_CMD_CC)\\$(LIBTOOL) --tag=CC --mode=compile \\$(CC) \\$(CFLAGS) \\$(EXTRA_CFLAGS) $DEPENDENCY_TRACKING_OPTIONS -c \\$< -o \\$@" ;\
   4.112 +        done`
   4.113  fi
   4.114  
   4.115  OBJECTS=`echo $SOURCES`
     5.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     5.2 +++ b/wayland-protocols/pointer-constraints-unstable-v1.xml	Mon Jun 25 09:37:25 2018 -0700
     5.3 @@ -0,0 +1,339 @@
     5.4 +<?xml version="1.0" encoding="UTF-8"?>
     5.5 +<protocol name="pointer_constraints_unstable_v1">
     5.6 +
     5.7 +  <copyright>
     5.8 +    Copyright © 2014      Jonas Ådahl
     5.9 +    Copyright © 2015      Red Hat Inc.
    5.10 +
    5.11 +    Permission is hereby granted, free of charge, to any person obtaining a
    5.12 +    copy of this software and associated documentation files (the "Software"),
    5.13 +    to deal in the Software without restriction, including without limitation
    5.14 +    the rights to use, copy, modify, merge, publish, distribute, sublicense,
    5.15 +    and/or sell copies of the Software, and to permit persons to whom the
    5.16 +    Software is furnished to do so, subject to the following conditions:
    5.17 +
    5.18 +    The above copyright notice and this permission notice (including the next
    5.19 +    paragraph) shall be included in all copies or substantial portions of the
    5.20 +    Software.
    5.21 +
    5.22 +    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    5.23 +    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    5.24 +    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
    5.25 +    THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
    5.26 +    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
    5.27 +    FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
    5.28 +    DEALINGS IN THE SOFTWARE.
    5.29 +  </copyright>
    5.30 +
    5.31 +  <description summary="protocol for constraining pointer motions">
    5.32 +    This protocol specifies a set of interfaces used for adding constraints to
    5.33 +    the motion of a pointer. Possible constraints include confining pointer
    5.34 +    motions to a given region, or locking it to its current position.
    5.35 +
    5.36 +    In order to constrain the pointer, a client must first bind the global
    5.37 +    interface "wp_pointer_constraints" which, if a compositor supports pointer
    5.38 +    constraints, is exposed by the registry. Using the bound global object, the
    5.39 +    client uses the request that corresponds to the type of constraint it wants
    5.40 +    to make. See wp_pointer_constraints for more details.
    5.41 +
    5.42 +    Warning! The protocol described in this file is experimental and backward
    5.43 +    incompatible changes may be made. Backward compatible changes may be added
    5.44 +    together with the corresponding interface version bump. Backward
    5.45 +    incompatible changes are done by bumping the version number in the protocol
    5.46 +    and interface names and resetting the interface version. Once the protocol
    5.47 +    is to be declared stable, the 'z' prefix and the version number in the
    5.48 +    protocol and interface names are removed and the interface version number is
    5.49 +    reset.
    5.50 +  </description>
    5.51 +
    5.52 +  <interface name="zwp_pointer_constraints_v1" version="1">
    5.53 +    <description summary="constrain the movement of a pointer">
    5.54 +      The global interface exposing pointer constraining functionality. It
    5.55 +      exposes two requests: lock_pointer for locking the pointer to its
    5.56 +      position, and confine_pointer for locking the pointer to a region.
    5.57 +
    5.58 +      The lock_pointer and confine_pointer requests create the objects
    5.59 +      wp_locked_pointer and wp_confined_pointer respectively, and the client can
    5.60 +      use these objects to interact with the lock.
    5.61 +
    5.62 +      For any surface, only one lock or confinement may be active across all
    5.63 +      wl_pointer objects of the same seat. If a lock or confinement is requested
    5.64 +      when another lock or confinement is active or requested on the same surface
    5.65 +      and with any of the wl_pointer objects of the same seat, an
    5.66 +      'already_constrained' error will be raised.
    5.67 +    </description>
    5.68 +
    5.69 +    <enum name="error">
    5.70 +      <description summary="wp_pointer_constraints error values">
    5.71 +	These errors can be emitted in response to wp_pointer_constraints
    5.72 +	requests.
    5.73 +      </description>
    5.74 +      <entry name="already_constrained" value="1"
    5.75 +	     summary="pointer constraint already requested on that surface"/>
    5.76 +    </enum>
    5.77 +
    5.78 +    <enum name="lifetime">
    5.79 +      <description summary="constraint lifetime">
    5.80 +	These values represent different lifetime semantics. They are passed
    5.81 +	as arguments to the factory requests to specify how the constraint
    5.82 +	lifetimes should be managed.
    5.83 +      </description>
    5.84 +      <entry name="oneshot" value="1">
    5.85 +	<description summary="the pointer constraint is defunct once deactivated">
    5.86 +	  A oneshot pointer constraint will never reactivate once it has been
    5.87 +	  deactivated. See the corresponding deactivation event
    5.88 +	  (wp_locked_pointer.unlocked and wp_confined_pointer.unconfined) for
    5.89 +	  details.
    5.90 +	</description>
    5.91 +      </entry>
    5.92 +      <entry name="persistent" value="2">
    5.93 +	<description summary="the pointer constraint may reactivate">
    5.94 +	  A persistent pointer constraint may again reactivate once it has
    5.95 +	  been deactivated. See the corresponding deactivation event
    5.96 +	  (wp_locked_pointer.unlocked and wp_confined_pointer.unconfined) for
    5.97 +	  details.
    5.98 +	</description>
    5.99 +      </entry>
   5.100 +    </enum>
   5.101 +
   5.102 +    <request name="destroy" type="destructor">
   5.103 +      <description summary="destroy the pointer constraints manager object">
   5.104 +	Used by the client to notify the server that it will no longer use this
   5.105 +	pointer constraints object.
   5.106 +      </description>
   5.107 +    </request>
   5.108 +
   5.109 +    <request name="lock_pointer">
   5.110 +      <description summary="lock pointer to a position">
   5.111 +	The lock_pointer request lets the client request to disable movements of
   5.112 +	the virtual pointer (i.e. the cursor), effectively locking the pointer
   5.113 +	to a position. This request may not take effect immediately; in the
   5.114 +	future, when the compositor deems implementation-specific constraints
   5.115 +	are satisfied, the pointer lock will be activated and the compositor
   5.116 +	sends a locked event.
   5.117 +
   5.118 +	The protocol provides no guarantee that the constraints are ever
   5.119 +	satisfied, and does not require the compositor to send an error if the
   5.120 +	constraints cannot ever be satisfied. It is thus possible to request a
   5.121 +	lock that will never activate.
   5.122 +
   5.123 +	There may not be another pointer constraint of any kind requested or
   5.124 +	active on the surface for any of the wl_pointer objects of the seat of
   5.125 +	the passed pointer when requesting a lock. If there is, an error will be
   5.126 +	raised. See general pointer lock documentation for more details.
   5.127 +
   5.128 +	The intersection of the region passed with this request and the input
   5.129 +	region of the surface is used to determine where the pointer must be
   5.130 +	in order for the lock to activate. It is up to the compositor whether to
   5.131 +	warp the pointer or require some kind of user interaction for the lock
   5.132 +	to activate. If the region is null the surface input region is used.
   5.133 +
   5.134 +	A surface may receive pointer focus without the lock being activated.
   5.135 +
   5.136 +	The request creates a new object wp_locked_pointer which is used to
   5.137 +	interact with the lock as well as receive updates about its state. See
   5.138 +	the the description of wp_locked_pointer for further information.
   5.139 +
   5.140 +	Note that while a pointer is locked, the wl_pointer objects of the
   5.141 +	corresponding seat will not emit any wl_pointer.motion events, but
   5.142 +	relative motion events will still be emitted via wp_relative_pointer
   5.143 +	objects of the same seat. wl_pointer.axis and wl_pointer.button events
   5.144 +	are unaffected.
   5.145 +      </description>
   5.146 +      <arg name="id" type="new_id" interface="zwp_locked_pointer_v1"/>
   5.147 +      <arg name="surface" type="object" interface="wl_surface"
   5.148 +	   summary="surface to lock pointer to"/>
   5.149 +      <arg name="pointer" type="object" interface="wl_pointer"
   5.150 +	   summary="the pointer that should be locked"/>
   5.151 +      <arg name="region" type="object" interface="wl_region" allow-null="true"
   5.152 +	   summary="region of surface"/>
   5.153 +      <arg name="lifetime" type="uint" summary="lock lifetime"/>
   5.154 +    </request>
   5.155 +
   5.156 +    <request name="confine_pointer">
   5.157 +      <description summary="confine pointer to a region">
   5.158 +	The confine_pointer request lets the client request to confine the
   5.159 +	pointer cursor to a given region. This request may not take effect
   5.160 +	immediately; in the future, when the compositor deems implementation-
   5.161 +	specific constraints are satisfied, the pointer confinement will be
   5.162 +	activated and the compositor sends a confined event.
   5.163 +
   5.164 +	The intersection of the region passed with this request and the input
   5.165 +	region of the surface is used to determine where the pointer must be
   5.166 +	in order for the confinement to activate. It is up to the compositor
   5.167 +	whether to warp the pointer or require some kind of user interaction for
   5.168 +	the confinement to activate. If the region is null the surface input
   5.169 +	region is used.
   5.170 +
   5.171 +	The request will create a new object wp_confined_pointer which is used
   5.172 +	to interact with the confinement as well as receive updates about its
   5.173 +	state. See the the description of wp_confined_pointer for further
   5.174 +	information.
   5.175 +      </description>
   5.176 +      <arg name="id" type="new_id" interface="zwp_confined_pointer_v1"/>
   5.177 +      <arg name="surface" type="object" interface="wl_surface"
   5.178 +	   summary="surface to lock pointer to"/>
   5.179 +      <arg name="pointer" type="object" interface="wl_pointer"
   5.180 +	   summary="the pointer that should be confined"/>
   5.181 +      <arg name="region" type="object" interface="wl_region" allow-null="true"
   5.182 +	   summary="region of surface"/>
   5.183 +      <arg name="lifetime" type="uint" summary="confinement lifetime"/>
   5.184 +    </request>
   5.185 +  </interface>
   5.186 +
   5.187 +  <interface name="zwp_locked_pointer_v1" version="1">
   5.188 +    <description summary="receive relative pointer motion events">
   5.189 +      The wp_locked_pointer interface represents a locked pointer state.
   5.190 +
   5.191 +      While the lock of this object is active, the wl_pointer objects of the
   5.192 +      associated seat will not emit any wl_pointer.motion events.
   5.193 +
   5.194 +      This object will send the event 'locked' when the lock is activated.
   5.195 +      Whenever the lock is activated, it is guaranteed that the locked surface
   5.196 +      will already have received pointer focus and that the pointer will be
   5.197 +      within the region passed to the request creating this object.
   5.198 +
   5.199 +      To unlock the pointer, send the destroy request. This will also destroy
   5.200 +      the wp_locked_pointer object.
   5.201 +
   5.202 +      If the compositor decides to unlock the pointer the unlocked event is
   5.203 +      sent. See wp_locked_pointer.unlock for details.
   5.204 +
   5.205 +      When unlocking, the compositor may warp the cursor position to the set
   5.206 +      cursor position hint. If it does, it will not result in any relative
   5.207 +      motion events emitted via wp_relative_pointer.
   5.208 +
   5.209 +      If the surface the lock was requested on is destroyed and the lock is not
   5.210 +      yet activated, the wp_locked_pointer object is now defunct and must be
   5.211 +      destroyed.
   5.212 +    </description>
   5.213 +
   5.214 +    <request name="destroy" type="destructor">
   5.215 +      <description summary="destroy the locked pointer object">
   5.216 +	Destroy the locked pointer object. If applicable, the compositor will
   5.217 +	unlock the pointer.
   5.218 +      </description>
   5.219 +    </request>
   5.220 +
   5.221 +    <request name="set_cursor_position_hint">
   5.222 +      <description summary="set the pointer cursor position hint">
   5.223 +	Set the cursor position hint relative to the top left corner of the
   5.224 +	surface.
   5.225 +
   5.226 +	If the client is drawing its own cursor, it should update the position
   5.227 +	hint to the position of its own cursor. A compositor may use this
   5.228 +	information to warp the pointer upon unlock in order to avoid pointer
   5.229 +	jumps.
   5.230 +
   5.231 +	The cursor position hint is double buffered. The new hint will only take
   5.232 +	effect when the associated surface gets it pending state applied. See
   5.233 +	wl_surface.commit for details.
   5.234 +      </description>
   5.235 +      <arg name="surface_x" type="fixed"
   5.236 +	   summary="surface-local x coordinate"/>
   5.237 +      <arg name="surface_y" type="fixed"
   5.238 +	   summary="surface-local y coordinate"/>
   5.239 +    </request>
   5.240 +
   5.241 +    <request name="set_region">
   5.242 +      <description summary="set a new lock region">
   5.243 +	Set a new region used to lock the pointer.
   5.244 +
   5.245 +	The new lock region is double-buffered. The new lock region will
   5.246 +	only take effect when the associated surface gets its pending state
   5.247 +	applied. See wl_surface.commit for details.
   5.248 +
   5.249 +	For details about the lock region, see wp_locked_pointer.
   5.250 +      </description>
   5.251 +      <arg name="region" type="object" interface="wl_region" allow-null="true"
   5.252 +	   summary="region of surface"/>
   5.253 +    </request>
   5.254 +
   5.255 +    <event name="locked">
   5.256 +      <description summary="lock activation event">
   5.257 +	Notification that the pointer lock of the seat's pointer is activated.
   5.258 +      </description>
   5.259 +    </event>
   5.260 +
   5.261 +    <event name="unlocked">
   5.262 +      <description summary="lock deactivation event">
   5.263 +	Notification that the pointer lock of the seat's pointer is no longer
   5.264 +	active. If this is a oneshot pointer lock (see
   5.265 +	wp_pointer_constraints.lifetime) this object is now defunct and should
   5.266 +	be destroyed. If this is a persistent pointer lock (see
   5.267 +	wp_pointer_constraints.lifetime) this pointer lock may again
   5.268 +	reactivate in the future.
   5.269 +      </description>
   5.270 +    </event>
   5.271 +  </interface>
   5.272 +
   5.273 +  <interface name="zwp_confined_pointer_v1" version="1">
   5.274 +    <description summary="confined pointer object">
   5.275 +      The wp_confined_pointer interface represents a confined pointer state.
   5.276 +
   5.277 +      This object will send the event 'confined' when the confinement is
   5.278 +      activated. Whenever the confinement is activated, it is guaranteed that
   5.279 +      the surface the pointer is confined to will already have received pointer
   5.280 +      focus and that the pointer will be within the region passed to the request
   5.281 +      creating this object. It is up to the compositor to decide whether this
   5.282 +      requires some user interaction and if the pointer will warp to within the
   5.283 +      passed region if outside.
   5.284 +
   5.285 +      To unconfine the pointer, send the destroy request. This will also destroy
   5.286 +      the wp_confined_pointer object.
   5.287 +
   5.288 +      If the compositor decides to unconfine the pointer the unconfined event is
   5.289 +      sent. The wp_confined_pointer object is at this point defunct and should
   5.290 +      be destroyed.
   5.291 +    </description>
   5.292 +
   5.293 +    <request name="destroy" type="destructor">
   5.294 +      <description summary="destroy the confined pointer object">
   5.295 +	Destroy the confined pointer object. If applicable, the compositor will
   5.296 +	unconfine the pointer.
   5.297 +      </description>
   5.298 +    </request>
   5.299 +
   5.300 +    <request name="set_region">
   5.301 +      <description summary="set a new confine region">
   5.302 +	Set a new region used to confine the pointer.
   5.303 +
   5.304 +	The new confine region is double-buffered. The new confine region will
   5.305 +	only take effect when the associated surface gets its pending state
   5.306 +	applied. See wl_surface.commit for details.
   5.307 +
   5.308 +	If the confinement is active when the new confinement region is applied
   5.309 +	and the pointer ends up outside of newly applied region, the pointer may
   5.310 +	warped to a position within the new confinement region. If warped, a
   5.311 +	wl_pointer.motion event will be emitted, but no
   5.312 +	wp_relative_pointer.relative_motion event.
   5.313 +
   5.314 +	The compositor may also, instead of using the new region, unconfine the
   5.315 +	pointer.
   5.316 +
   5.317 +	For details about the confine region, see wp_confined_pointer.
   5.318 +      </description>
   5.319 +      <arg name="region" type="object" interface="wl_region" allow-null="true"
   5.320 +	   summary="region of surface"/>
   5.321 +    </request>
   5.322 +
   5.323 +    <event name="confined">
   5.324 +      <description summary="pointer confined">
   5.325 +	Notification that the pointer confinement of the seat's pointer is
   5.326 +	activated.
   5.327 +      </description>
   5.328 +    </event>
   5.329 +
   5.330 +    <event name="unconfined">
   5.331 +      <description summary="pointer unconfined">
   5.332 +	Notification that the pointer confinement of the seat's pointer is no
   5.333 +	longer active. If this is a oneshot pointer confinement (see
   5.334 +	wp_pointer_constraints.lifetime) this object is now defunct and should
   5.335 +	be destroyed. If this is a persistent pointer confinement (see
   5.336 +	wp_pointer_constraints.lifetime) this pointer confinement may again
   5.337 +	reactivate in the future.
   5.338 +      </description>
   5.339 +    </event>
   5.340 +  </interface>
   5.341 +
   5.342 +</protocol>
     6.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     6.2 +++ b/wayland-protocols/relative-pointer-unstable-v1.xml	Mon Jun 25 09:37:25 2018 -0700
     6.3 @@ -0,0 +1,136 @@
     6.4 +<?xml version="1.0" encoding="UTF-8"?>
     6.5 +<protocol name="relative_pointer_unstable_v1">
     6.6 +
     6.7 +  <copyright>
     6.8 +    Copyright © 2014      Jonas Ådahl
     6.9 +    Copyright © 2015      Red Hat Inc.
    6.10 +
    6.11 +    Permission is hereby granted, free of charge, to any person obtaining a
    6.12 +    copy of this software and associated documentation files (the "Software"),
    6.13 +    to deal in the Software without restriction, including without limitation
    6.14 +    the rights to use, copy, modify, merge, publish, distribute, sublicense,
    6.15 +    and/or sell copies of the Software, and to permit persons to whom the
    6.16 +    Software is furnished to do so, subject to the following conditions:
    6.17 +
    6.18 +    The above copyright notice and this permission notice (including the next
    6.19 +    paragraph) shall be included in all copies or substantial portions of the
    6.20 +    Software.
    6.21 +
    6.22 +    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    6.23 +    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    6.24 +    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
    6.25 +    THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
    6.26 +    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
    6.27 +    FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
    6.28 +    DEALINGS IN THE SOFTWARE.
    6.29 +  </copyright>
    6.30 +
    6.31 +  <description summary="protocol for relative pointer motion events">
    6.32 +    This protocol specifies a set of interfaces used for making clients able to
    6.33 +    receive relative pointer events not obstructed by barriers (such as the
    6.34 +    monitor edge or other pointer barriers).
    6.35 +
    6.36 +    To start receiving relative pointer events, a client must first bind the
    6.37 +    global interface "wp_relative_pointer_manager" which, if a compositor
    6.38 +    supports relative pointer motion events, is exposed by the registry. After
    6.39 +    having created the relative pointer manager proxy object, the client uses
    6.40 +    it to create the actual relative pointer object using the
    6.41 +    "get_relative_pointer" request given a wl_pointer. The relative pointer
    6.42 +    motion events will then, when applicable, be transmitted via the proxy of
    6.43 +    the newly created relative pointer object. See the documentation of the
    6.44 +    relative pointer interface for more details.
    6.45 +
    6.46 +    Warning! The protocol described in this file is experimental and backward
    6.47 +    incompatible changes may be made. Backward compatible changes may be added
    6.48 +    together with the corresponding interface version bump. Backward
    6.49 +    incompatible changes are done by bumping the version number in the protocol
    6.50 +    and interface names and resetting the interface version. Once the protocol
    6.51 +    is to be declared stable, the 'z' prefix and the version number in the
    6.52 +    protocol and interface names are removed and the interface version number is
    6.53 +    reset.
    6.54 +  </description>
    6.55 +
    6.56 +  <interface name="zwp_relative_pointer_manager_v1" version="1">
    6.57 +    <description summary="get relative pointer objects">
    6.58 +      A global interface used for getting the relative pointer object for a
    6.59 +      given pointer.
    6.60 +    </description>
    6.61 +
    6.62 +    <request name="destroy" type="destructor">
    6.63 +      <description summary="destroy the relative pointer manager object">
    6.64 +	Used by the client to notify the server that it will no longer use this
    6.65 +	relative pointer manager object.
    6.66 +      </description>
    6.67 +    </request>
    6.68 +
    6.69 +    <request name="get_relative_pointer">
    6.70 +      <description summary="get a relative pointer object">
    6.71 +	Create a relative pointer interface given a wl_pointer object. See the
    6.72 +	wp_relative_pointer interface for more details.
    6.73 +      </description>
    6.74 +      <arg name="id" type="new_id" interface="zwp_relative_pointer_v1"/>
    6.75 +      <arg name="pointer" type="object" interface="wl_pointer"/>
    6.76 +    </request>
    6.77 +  </interface>
    6.78 +
    6.79 +  <interface name="zwp_relative_pointer_v1" version="1">
    6.80 +    <description summary="relative pointer object">
    6.81 +      A wp_relative_pointer object is an extension to the wl_pointer interface
    6.82 +      used for emitting relative pointer events. It shares the same focus as
    6.83 +      wl_pointer objects of the same seat and will only emit events when it has
    6.84 +      focus.
    6.85 +    </description>
    6.86 +
    6.87 +    <request name="destroy" type="destructor">
    6.88 +      <description summary="release the relative pointer object"/>
    6.89 +    </request>
    6.90 +
    6.91 +    <event name="relative_motion">
    6.92 +      <description summary="relative pointer motion">
    6.93 +	Relative x/y pointer motion from the pointer of the seat associated with
    6.94 +	this object.
    6.95 +
    6.96 +	A relative motion is in the same dimension as regular wl_pointer motion
    6.97 +	events, except they do not represent an absolute position. For example,
    6.98 +	moving a pointer from (x, y) to (x', y') would have the equivalent
    6.99 +	relative motion (x' - x, y' - y). If a pointer motion caused the
   6.100 +	absolute pointer position to be clipped by for example the edge of the
   6.101 +	monitor, the relative motion is unaffected by the clipping and will
   6.102 +	represent the unclipped motion.
   6.103 +
   6.104 +	This event also contains non-accelerated motion deltas. The
   6.105 +	non-accelerated delta is, when applicable, the regular pointer motion
   6.106 +	delta as it was before having applied motion acceleration and other
   6.107 +	transformations such as normalization.
   6.108 +
   6.109 +	Note that the non-accelerated delta does not represent 'raw' events as
   6.110 +	they were read from some device. Pointer motion acceleration is device-
   6.111 +	and configuration-specific and non-accelerated deltas and accelerated
   6.112 +	deltas may have the same value on some devices.
   6.113 +
   6.114 +	Relative motions are not coupled to wl_pointer.motion events, and can be
   6.115 +	sent in combination with such events, but also independently. There may
   6.116 +	also be scenarios where wl_pointer.motion is sent, but there is no
   6.117 +	relative motion. The order of an absolute and relative motion event
   6.118 +	originating from the same physical motion is not guaranteed.
   6.119 +
   6.120 +	If the client needs button events or focus state, it can receive them
   6.121 +	from a wl_pointer object of the same seat that the wp_relative_pointer
   6.122 +	object is associated with.
   6.123 +      </description>
   6.124 +      <arg name="utime_hi" type="uint"
   6.125 +	   summary="high 32 bits of a 64 bit timestamp with microsecond granularity"/>
   6.126 +      <arg name="utime_lo" type="uint"
   6.127 +	   summary="low 32 bits of a 64 bit timestamp with microsecond granularity"/>
   6.128 +      <arg name="dx" type="fixed"
   6.129 +	   summary="the x component of the motion vector"/>
   6.130 +      <arg name="dy" type="fixed"
   6.131 +	   summary="the y component of the motion vector"/>
   6.132 +      <arg name="dx_unaccel" type="fixed"
   6.133 +	   summary="the x component of the unaccelerated motion vector"/>
   6.134 +      <arg name="dy_unaccel" type="fixed"
   6.135 +	   summary="the y component of the unaccelerated motion vector"/>
   6.136 +    </event>
   6.137 +  </interface>
   6.138 +
   6.139 +</protocol>
     7.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     7.2 +++ b/wayland-protocols/wayland.xml	Mon Jun 25 09:37:25 2018 -0700
     7.3 @@ -0,0 +1,2746 @@
     7.4 +<?xml version="1.0" encoding="UTF-8"?>
     7.5 +<protocol name="wayland">
     7.6 +
     7.7 +  <copyright>
     7.8 +    Copyright © 2008-2011 Kristian Høgsberg
     7.9 +    Copyright © 2010-2011 Intel Corporation
    7.10 +    Copyright © 2012-2013 Collabora, Ltd.
    7.11 +
    7.12 +    Permission is hereby granted, free of charge, to any person
    7.13 +    obtaining a copy of this software and associated documentation files
    7.14 +    (the "Software"), to deal in the Software without restriction,
    7.15 +    including without limitation the rights to use, copy, modify, merge,
    7.16 +    publish, distribute, sublicense, and/or sell copies of the Software,
    7.17 +    and to permit persons to whom the Software is furnished to do so,
    7.18 +    subject to the following conditions:
    7.19 +
    7.20 +    The above copyright notice and this permission notice (including the
    7.21 +    next paragraph) shall be included in all copies or substantial
    7.22 +    portions of the Software.
    7.23 +
    7.24 +    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
    7.25 +    EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
    7.26 +    MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
    7.27 +    NONINFRINGEMENT.  IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
    7.28 +    BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
    7.29 +    ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
    7.30 +    CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
    7.31 +    SOFTWARE.
    7.32 +  </copyright>
    7.33 +
    7.34 +  <interface name="wl_display" version="1">
    7.35 +    <description summary="core global object">
    7.36 +      The core global object.  This is a special singleton object.  It
    7.37 +      is used for internal Wayland protocol features.
    7.38 +    </description>
    7.39 +
    7.40 +    <request name="sync">
    7.41 +      <description summary="asynchronous roundtrip">
    7.42 +	The sync request asks the server to emit the 'done' event
    7.43 +	on the returned wl_callback object.  Since requests are
    7.44 +	handled in-order and events are delivered in-order, this can
    7.45 +	be used as a barrier to ensure all previous requests and the
    7.46 +	resulting events have been handled.
    7.47 +
    7.48 +	The object returned by this request will be destroyed by the
    7.49 +	compositor after the callback is fired and as such the client must not
    7.50 +	attempt to use it after that point.
    7.51 +
    7.52 +	The callback_data passed in the callback is the event serial.
    7.53 +      </description>
    7.54 +      <arg name="callback" type="new_id" interface="wl_callback"
    7.55 +	   summary="callback object for the sync request"/>
    7.56 +    </request>
    7.57 +
    7.58 +    <request name="get_registry">
    7.59 +      <description summary="get global registry object">
    7.60 +	This request creates a registry object that allows the client
    7.61 +	to list and bind the global objects available from the
    7.62 +	compositor.
    7.63 +      </description>
    7.64 +      <arg name="registry" type="new_id" interface="wl_registry"
    7.65 +	   summary="global registry object"/>
    7.66 +    </request>
    7.67 +
    7.68 +    <event name="error">
    7.69 +      <description summary="fatal error event">
    7.70 +	The error event is sent out when a fatal (non-recoverable)
    7.71 +	error has occurred.  The object_id argument is the object
    7.72 +	where the error occurred, most often in response to a request
    7.73 +	to that object.  The code identifies the error and is defined
    7.74 +	by the object interface.  As such, each interface defines its
    7.75 +	own set of error codes.  The message is a brief description
    7.76 +	of the error, for (debugging) convenience.
    7.77 +      </description>
    7.78 +      <arg name="object_id" type="object" summary="object where the error occurred"/>
    7.79 +      <arg name="code" type="uint" summary="error code"/>
    7.80 +      <arg name="message" type="string" summary="error description"/>
    7.81 +    </event>
    7.82 +
    7.83 +    <enum name="error">
    7.84 +      <description summary="global error values">
    7.85 +	These errors are global and can be emitted in response to any
    7.86 +	server request.
    7.87 +      </description>
    7.88 +      <entry name="invalid_object" value="0"
    7.89 +	     summary="server couldn't find object"/>
    7.90 +      <entry name="invalid_method" value="1"
    7.91 +	     summary="method doesn't exist on the specified interface"/>
    7.92 +      <entry name="no_memory" value="2"
    7.93 +	     summary="server is out of memory"/>
    7.94 +    </enum>
    7.95 +
    7.96 +    <event name="delete_id">
    7.97 +      <description summary="acknowledge object ID deletion">
    7.98 +	This event is used internally by the object ID management
    7.99 +	logic.  When a client deletes an object, the server will send
   7.100 +	this event to acknowledge that it has seen the delete request.
   7.101 +	When the client receives this event, it will know that it can
   7.102 +	safely reuse the object ID.
   7.103 +      </description>
   7.104 +      <arg name="id" type="uint" summary="deleted object ID"/>
   7.105 +    </event>
   7.106 +  </interface>
   7.107 +
   7.108 +  <interface name="wl_registry" version="1">
   7.109 +    <description summary="global registry object">
   7.110 +      The singleton global registry object.  The server has a number of
   7.111 +      global objects that are available to all clients.  These objects
   7.112 +      typically represent an actual object in the server (for example,
   7.113 +      an input device) or they are singleton objects that provide
   7.114 +      extension functionality.
   7.115 +
   7.116 +      When a client creates a registry object, the registry object
   7.117 +      will emit a global event for each global currently in the
   7.118 +      registry.  Globals come and go as a result of device or
   7.119 +      monitor hotplugs, reconfiguration or other events, and the
   7.120 +      registry will send out global and global_remove events to
   7.121 +      keep the client up to date with the changes.  To mark the end
   7.122 +      of the initial burst of events, the client can use the
   7.123 +      wl_display.sync request immediately after calling
   7.124 +      wl_display.get_registry.
   7.125 +
   7.126 +      A client can bind to a global object by using the bind
   7.127 +      request.  This creates a client-side handle that lets the object
   7.128 +      emit events to the client and lets the client invoke requests on
   7.129 +      the object.
   7.130 +    </description>
   7.131 +
   7.132 +    <request name="bind">
   7.133 +      <description summary="bind an object to the display">
   7.134 +	Binds a new, client-created object to the server using the
   7.135 +	specified name as the identifier.
   7.136 +      </description>
   7.137 +      <arg name="name" type="uint" summary="unique numeric name of the object"/>
   7.138 +      <arg name="id" type="new_id" summary="bounded object"/>
   7.139 +    </request>
   7.140 +
   7.141 +    <event name="global">
   7.142 +      <description summary="announce global object">
   7.143 +	Notify the client of global objects.
   7.144 +
   7.145 +	The event notifies the client that a global object with
   7.146 +	the given name is now available, and it implements the
   7.147 +	given version of the given interface.
   7.148 +      </description>
   7.149 +      <arg name="name" type="uint" summary="numeric name of the global object"/>
   7.150 +      <arg name="interface" type="string" summary="interface implemented by the object"/>
   7.151 +      <arg name="version" type="uint" summary="interface version"/>
   7.152 +    </event>
   7.153 +
   7.154 +    <event name="global_remove">
   7.155 +      <description summary="announce removal of global object">
   7.156 +	Notify the client of removed global objects.
   7.157 +
   7.158 +	This event notifies the client that the global identified
   7.159 +	by name is no longer available.  If the client bound to
   7.160 +	the global using the bind request, the client should now
   7.161 +	destroy that object.
   7.162 +
   7.163 +	The object remains valid and requests to the object will be
   7.164 +	ignored until the client destroys it, to avoid races between
   7.165 +	the global going away and a client sending a request to it.
   7.166 +      </description>
   7.167 +      <arg name="name" type="uint" summary="numeric name of the global object"/>
   7.168 +    </event>
   7.169 +  </interface>
   7.170 +
   7.171 +  <interface name="wl_callback" version="1">
   7.172 +    <description summary="callback object">
   7.173 +      Clients can handle the 'done' event to get notified when
   7.174 +      the related request is done.
   7.175 +    </description>
   7.176 +
   7.177 +    <event name="done">
   7.178 +      <description summary="done event">
   7.179 +	Notify the client when the related request is done.
   7.180 +      </description>
   7.181 +      <arg name="callback_data" type="uint" summary="request-specific data for the callback"/>
   7.182 +    </event>
   7.183 +  </interface>
   7.184 +
   7.185 +  <interface name="wl_compositor" version="4">
   7.186 +    <description summary="the compositor singleton">
   7.187 +      A compositor.  This object is a singleton global.  The
   7.188 +      compositor is in charge of combining the contents of multiple
   7.189 +      surfaces into one displayable output.
   7.190 +    </description>
   7.191 +
   7.192 +    <request name="create_surface">
   7.193 +      <description summary="create new surface">
   7.194 +	Ask the compositor to create a new surface.
   7.195 +      </description>
   7.196 +      <arg name="id" type="new_id" interface="wl_surface" summary="the new surface"/>
   7.197 +    </request>
   7.198 +
   7.199 +    <request name="create_region">
   7.200 +      <description summary="create new region">
   7.201 +	Ask the compositor to create a new region.
   7.202 +      </description>
   7.203 +      <arg name="id" type="new_id" interface="wl_region" summary="the new region"/>
   7.204 +    </request>
   7.205 +  </interface>
   7.206 +
   7.207 +  <interface name="wl_shm_pool" version="1">
   7.208 +    <description summary="a shared memory pool">
   7.209 +      The wl_shm_pool object encapsulates a piece of memory shared
   7.210 +      between the compositor and client.  Through the wl_shm_pool
   7.211 +      object, the client can allocate shared memory wl_buffer objects.
   7.212 +      All objects created through the same pool share the same
   7.213 +      underlying mapped memory. Reusing the mapped memory avoids the
   7.214 +      setup/teardown overhead and is useful when interactively resizing
   7.215 +      a surface or for many small buffers.
   7.216 +    </description>
   7.217 +
   7.218 +    <request name="create_buffer">
   7.219 +      <description summary="create a buffer from the pool">
   7.220 +	Create a wl_buffer object from the pool.
   7.221 +
   7.222 +	The buffer is created offset bytes into the pool and has
   7.223 +	width and height as specified.  The stride argument specifies
   7.224 +	the number of bytes from the beginning of one row to the beginning
   7.225 +	of the next.  The format is the pixel format of the buffer and
   7.226 +	must be one of those advertised through the wl_shm.format event.
   7.227 +
   7.228 +	A buffer will keep a reference to the pool it was created from
   7.229 +	so it is valid to destroy the pool immediately after creating
   7.230 +	a buffer from it.
   7.231 +      </description>
   7.232 +      <arg name="id" type="new_id" interface="wl_buffer" summary="buffer to create"/>
   7.233 +      <arg name="offset" type="int" summary="buffer byte offset within the pool"/>
   7.234 +      <arg name="width" type="int" summary="buffer width, in pixels"/>
   7.235 +      <arg name="height" type="int" summary="buffer height, in pixels"/>
   7.236 +      <arg name="stride" type="int" summary="number of bytes from the beginning of one row to the beginning of the next row"/>
   7.237 +      <arg name="format" type="uint" enum="wl_shm.format" summary="buffer pixel format"/>
   7.238 +    </request>
   7.239 +
   7.240 +    <request name="destroy" type="destructor">
   7.241 +      <description summary="destroy the pool">
   7.242 +	Destroy the shared memory pool.
   7.243 +
   7.244 +	The mmapped memory will be released when all
   7.245 +	buffers that have been created from this pool
   7.246 +	are gone.
   7.247 +      </description>
   7.248 +    </request>
   7.249 +
   7.250 +    <request name="resize">
   7.251 +      <description summary="change the size of the pool mapping">
   7.252 +	This request will cause the server to remap the backing memory
   7.253 +	for the pool from the file descriptor passed when the pool was
   7.254 +	created, but using the new size.  This request can only be
   7.255 +	used to make the pool bigger.
   7.256 +      </description>
   7.257 +      <arg name="size" type="int" summary="new size of the pool, in bytes"/>
   7.258 +    </request>
   7.259 +  </interface>
   7.260 +
   7.261 +  <interface name="wl_shm" version="1">
   7.262 +    <description summary="shared memory support">
   7.263 +      A singleton global object that provides support for shared
   7.264 +      memory.
   7.265 +
   7.266 +      Clients can create wl_shm_pool objects using the create_pool
   7.267 +      request.
   7.268 +
   7.269 +      At connection setup time, the wl_shm object emits one or more
   7.270 +      format events to inform clients about the valid pixel formats
   7.271 +      that can be used for buffers.
   7.272 +    </description>
   7.273 +
   7.274 +    <enum name="error">
   7.275 +      <description summary="wl_shm error values">
   7.276 +	These errors can be emitted in response to wl_shm requests.
   7.277 +      </description>
   7.278 +      <entry name="invalid_format" value="0" summary="buffer format is not known"/>
   7.279 +      <entry name="invalid_stride" value="1" summary="invalid size or stride during pool or buffer creation"/>
   7.280 +      <entry name="invalid_fd" value="2" summary="mmapping the file descriptor failed"/>
   7.281 +    </enum>
   7.282 +
   7.283 +    <enum name="format">
   7.284 +      <description summary="pixel formats">
   7.285 +	This describes the memory layout of an individual pixel.
   7.286 +
   7.287 +	All renderers should support argb8888 and xrgb8888 but any other
   7.288 +	formats are optional and may not be supported by the particular
   7.289 +	renderer in use.
   7.290 +
   7.291 +	The drm format codes match the macros defined in drm_fourcc.h.
   7.292 +	The formats actually supported by the compositor will be
   7.293 +	reported by the format event.
   7.294 +      </description>
   7.295 +      <entry name="argb8888" value="0" summary="32-bit ARGB format, [31:0] A:R:G:B 8:8:8:8 little endian"/>
   7.296 +      <entry name="xrgb8888" value="1" summary="32-bit RGB format, [31:0] x:R:G:B 8:8:8:8 little endian"/>
   7.297 +      <entry name="c8" value="0x20203843" summary="8-bit color index format, [7:0] C"/>
   7.298 +      <entry name="rgb332" value="0x38424752" summary="8-bit RGB format, [7:0] R:G:B 3:3:2"/>
   7.299 +      <entry name="bgr233" value="0x38524742" summary="8-bit BGR format, [7:0] B:G:R 2:3:3"/>
   7.300 +      <entry name="xrgb4444" value="0x32315258" summary="16-bit xRGB format, [15:0] x:R:G:B 4:4:4:4 little endian"/>
   7.301 +      <entry name="xbgr4444" value="0x32314258" summary="16-bit xBGR format, [15:0] x:B:G:R 4:4:4:4 little endian"/>
   7.302 +      <entry name="rgbx4444" value="0x32315852" summary="16-bit RGBx format, [15:0] R:G:B:x 4:4:4:4 little endian"/>
   7.303 +      <entry name="bgrx4444" value="0x32315842" summary="16-bit BGRx format, [15:0] B:G:R:x 4:4:4:4 little endian"/>
   7.304 +      <entry name="argb4444" value="0x32315241" summary="16-bit ARGB format, [15:0] A:R:G:B 4:4:4:4 little endian"/>
   7.305 +      <entry name="abgr4444" value="0x32314241" summary="16-bit ABGR format, [15:0] A:B:G:R 4:4:4:4 little endian"/>
   7.306 +      <entry name="rgba4444" value="0x32314152" summary="16-bit RBGA format, [15:0] R:G:B:A 4:4:4:4 little endian"/>
   7.307 +      <entry name="bgra4444" value="0x32314142" summary="16-bit BGRA format, [15:0] B:G:R:A 4:4:4:4 little endian"/>
   7.308 +      <entry name="xrgb1555" value="0x35315258" summary="16-bit xRGB format, [15:0] x:R:G:B 1:5:5:5 little endian"/>
   7.309 +      <entry name="xbgr1555" value="0x35314258" summary="16-bit xBGR 1555 format, [15:0] x:B:G:R 1:5:5:5 little endian"/>
   7.310 +      <entry name="rgbx5551" value="0x35315852" summary="16-bit RGBx 5551 format, [15:0] R:G:B:x 5:5:5:1 little endian"/>
   7.311 +      <entry name="bgrx5551" value="0x35315842" summary="16-bit BGRx 5551 format, [15:0] B:G:R:x 5:5:5:1 little endian"/>
   7.312 +      <entry name="argb1555" value="0x35315241" summary="16-bit ARGB 1555 format, [15:0] A:R:G:B 1:5:5:5 little endian"/>
   7.313 +      <entry name="abgr1555" value="0x35314241" summary="16-bit ABGR 1555 format, [15:0] A:B:G:R 1:5:5:5 little endian"/>
   7.314 +      <entry name="rgba5551" value="0x35314152" summary="16-bit RGBA 5551 format, [15:0] R:G:B:A 5:5:5:1 little endian"/>
   7.315 +      <entry name="bgra5551" value="0x35314142" summary="16-bit BGRA 5551 format, [15:0] B:G:R:A 5:5:5:1 little endian"/>
   7.316 +      <entry name="rgb565" value="0x36314752" summary="16-bit RGB 565 format, [15:0] R:G:B 5:6:5 little endian"/>
   7.317 +      <entry name="bgr565" value="0x36314742" summary="16-bit BGR 565 format, [15:0] B:G:R 5:6:5 little endian"/>
   7.318 +      <entry name="rgb888" value="0x34324752" summary="24-bit RGB format, [23:0] R:G:B little endian"/>
   7.319 +      <entry name="bgr888" value="0x34324742" summary="24-bit BGR format, [23:0] B:G:R little endian"/>
   7.320 +      <entry name="xbgr8888" value="0x34324258" summary="32-bit xBGR format, [31:0] x:B:G:R 8:8:8:8 little endian"/>
   7.321 +      <entry name="rgbx8888" value="0x34325852" summary="32-bit RGBx format, [31:0] R:G:B:x 8:8:8:8 little endian"/>
   7.322 +      <entry name="bgrx8888" value="0x34325842" summary="32-bit BGRx format, [31:0] B:G:R:x 8:8:8:8 little endian"/>
   7.323 +      <entry name="abgr8888" value="0x34324241" summary="32-bit ABGR format, [31:0] A:B:G:R 8:8:8:8 little endian"/>
   7.324 +      <entry name="rgba8888" value="0x34324152" summary="32-bit RGBA format, [31:0] R:G:B:A 8:8:8:8 little endian"/>
   7.325 +      <entry name="bgra8888" value="0x34324142" summary="32-bit BGRA format, [31:0] B:G:R:A 8:8:8:8 little endian"/>
   7.326 +      <entry name="xrgb2101010" value="0x30335258" summary="32-bit xRGB format, [31:0] x:R:G:B 2:10:10:10 little endian"/>
   7.327 +      <entry name="xbgr2101010" value="0x30334258" summary="32-bit xBGR format, [31:0] x:B:G:R 2:10:10:10 little endian"/>
   7.328 +      <entry name="rgbx1010102" value="0x30335852" summary="32-bit RGBx format, [31:0] R:G:B:x 10:10:10:2 little endian"/>
   7.329 +      <entry name="bgrx1010102" value="0x30335842" summary="32-bit BGRx format, [31:0] B:G:R:x 10:10:10:2 little endian"/>
   7.330 +      <entry name="argb2101010" value="0x30335241" summary="32-bit ARGB format, [31:0] A:R:G:B 2:10:10:10 little endian"/>
   7.331 +      <entry name="abgr2101010" value="0x30334241" summary="32-bit ABGR format, [31:0] A:B:G:R 2:10:10:10 little endian"/>
   7.332 +      <entry name="rgba1010102" value="0x30334152" summary="32-bit RGBA format, [31:0] R:G:B:A 10:10:10:2 little endian"/>
   7.333 +      <entry name="bgra1010102" value="0x30334142" summary="32-bit BGRA format, [31:0] B:G:R:A 10:10:10:2 little endian"/>
   7.334 +      <entry name="yuyv" value="0x56595559" summary="packed YCbCr format, [31:0] Cr0:Y1:Cb0:Y0 8:8:8:8 little endian"/>
   7.335 +      <entry name="yvyu" value="0x55595659" summary="packed YCbCr format, [31:0] Cb0:Y1:Cr0:Y0 8:8:8:8 little endian"/>
   7.336 +      <entry name="uyvy" value="0x59565955" summary="packed YCbCr format, [31:0] Y1:Cr0:Y0:Cb0 8:8:8:8 little endian"/>
   7.337 +      <entry name="vyuy" value="0x59555956" summary="packed YCbCr format, [31:0] Y1:Cb0:Y0:Cr0 8:8:8:8 little endian"/>
   7.338 +      <entry name="ayuv" value="0x56555941" summary="packed AYCbCr format, [31:0] A:Y:Cb:Cr 8:8:8:8 little endian"/>
   7.339 +      <entry name="nv12" value="0x3231564e" summary="2 plane YCbCr Cr:Cb format, 2x2 subsampled Cr:Cb plane"/>
   7.340 +      <entry name="nv21" value="0x3132564e" summary="2 plane YCbCr Cb:Cr format, 2x2 subsampled Cb:Cr plane"/>
   7.341 +      <entry name="nv16" value="0x3631564e" summary="2 plane YCbCr Cr:Cb format, 2x1 subsampled Cr:Cb plane"/>
   7.342 +      <entry name="nv61" value="0x3136564e" summary="2 plane YCbCr Cb:Cr format, 2x1 subsampled Cb:Cr plane"/>
   7.343 +      <entry name="yuv410" value="0x39565559" summary="3 plane YCbCr format, 4x4 subsampled Cb (1) and Cr (2) planes"/>
   7.344 +      <entry name="yvu410" value="0x39555659" summary="3 plane YCbCr format, 4x4 subsampled Cr (1) and Cb (2) planes"/>
   7.345 +      <entry name="yuv411" value="0x31315559" summary="3 plane YCbCr format, 4x1 subsampled Cb (1) and Cr (2) planes"/>
   7.346 +      <entry name="yvu411" value="0x31315659" summary="3 plane YCbCr format, 4x1 subsampled Cr (1) and Cb (2) planes"/>
   7.347 +      <entry name="yuv420" value="0x32315559" summary="3 plane YCbCr format, 2x2 subsampled Cb (1) and Cr (2) planes"/>
   7.348 +      <entry name="yvu420" value="0x32315659" summary="3 plane YCbCr format, 2x2 subsampled Cr (1) and Cb (2) planes"/>
   7.349 +      <entry name="yuv422" value="0x36315559" summary="3 plane YCbCr format, 2x1 subsampled Cb (1) and Cr (2) planes"/>
   7.350 +      <entry name="yvu422" value="0x36315659" summary="3 plane YCbCr format, 2x1 subsampled Cr (1) and Cb (2) planes"/>
   7.351 +      <entry name="yuv444" value="0x34325559" summary="3 plane YCbCr format, non-subsampled Cb (1) and Cr (2) planes"/>
   7.352 +      <entry name="yvu444" value="0x34325659" summary="3 plane YCbCr format, non-subsampled Cr (1) and Cb (2) planes"/>
   7.353 +    </enum>
   7.354 +
   7.355 +    <request name="create_pool">
   7.356 +      <description summary="create a shm pool">
   7.357 +	Create a new wl_shm_pool object.
   7.358 +
   7.359 +	The pool can be used to create shared memory based buffer
   7.360 +	objects.  The server will mmap size bytes of the passed file
   7.361 +	descriptor, to use as backing memory for the pool.
   7.362 +      </description>
   7.363 +      <arg name="id" type="new_id" interface="wl_shm_pool" summary="pool to create"/>
   7.364 +      <arg name="fd" type="fd" summary="file descriptor for the pool"/>
   7.365 +      <arg name="size" type="int" summary="pool size, in bytes"/>
   7.366 +    </request>
   7.367 +
   7.368 +    <event name="format">
   7.369 +      <description summary="pixel format description">
   7.370 +	Informs the client about a valid pixel format that
   7.371 +	can be used for buffers. Known formats include
   7.372 +	argb8888 and xrgb8888.
   7.373 +      </description>
   7.374 +      <arg name="format" type="uint" enum="format" summary="buffer pixel format"/>
   7.375 +    </event>
   7.376 +  </interface>
   7.377 +
   7.378 +  <interface name="wl_buffer" version="1">
   7.379 +    <description summary="content for a wl_surface">
   7.380 +      A buffer provides the content for a wl_surface. Buffers are
   7.381 +      created through factory interfaces such as wl_drm, wl_shm or
   7.382 +      similar. It has a width and a height and can be attached to a
   7.383 +      wl_surface, but the mechanism by which a client provides and
   7.384 +      updates the contents is defined by the buffer factory interface.
   7.385 +    </description>
   7.386 +
   7.387 +    <request name="destroy" type="destructor">
   7.388 +      <description summary="destroy a buffer">
   7.389 +	Destroy a buffer. If and how you need to release the backing
   7.390 +	storage is defined by the buffer factory interface.
   7.391 +
   7.392 +	For possible side-effects to a surface, see wl_surface.attach.
   7.393 +      </description>
   7.394 +    </request>
   7.395 +
   7.396 +    <event name="release">
   7.397 +      <description summary="compositor releases buffer">
   7.398 +	Sent when this wl_buffer is no longer used by the compositor.
   7.399 +	The client is now free to reuse or destroy this buffer and its
   7.400 +	backing storage.
   7.401 +
   7.402 +	If a client receives a release event before the frame callback
   7.403 +	requested in the same wl_surface.commit that attaches this
   7.404 +	wl_buffer to a surface, then the client is immediately free to
   7.405 +	reuse the buffer and its backing storage, and does not need a
   7.406 +	second buffer for the next surface content update. Typically
   7.407 +	this is possible, when the compositor maintains a copy of the
   7.408 +	wl_surface contents, e.g. as a GL texture. This is an important
   7.409 +	optimization for GL(ES) compositors with wl_shm clients.
   7.410 +      </description>
   7.411 +    </event>
   7.412 +  </interface>
   7.413 +
   7.414 +  <interface name="wl_data_offer" version="3">
   7.415 +    <description summary="offer to transfer data">
   7.416 +      A wl_data_offer represents a piece of data offered for transfer
   7.417 +      by another client (the source client).  It is used by the
   7.418 +      copy-and-paste and drag-and-drop mechanisms.  The offer
   7.419 +      describes the different mime types that the data can be
   7.420 +      converted to and provides the mechanism for transferring the
   7.421 +      data directly from the source client.
   7.422 +    </description>
   7.423 +
   7.424 +    <enum name="error">
   7.425 +      <entry name="invalid_finish" value="0"
   7.426 +	     summary="finish request was called untimely"/>
   7.427 +      <entry name="invalid_action_mask" value="1"
   7.428 +	     summary="action mask contains invalid values"/>
   7.429 +      <entry name="invalid_action" value="2"
   7.430 +	     summary="action argument has an invalid value"/>
   7.431 +      <entry name="invalid_offer" value="3"
   7.432 +	     summary="offer doesn't accept this request"/>
   7.433 +    </enum>
   7.434 +
   7.435 +    <request name="accept">
   7.436 +      <description summary="accept one of the offered mime types">
   7.437 +	Indicate that the client can accept the given mime type, or
   7.438 +	NULL for not accepted.
   7.439 +
   7.440 +	For objects of version 2 or older, this request is used by the
   7.441 +	client to give feedback whether the client can receive the given
   7.442 +	mime type, or NULL if none is accepted; the feedback does not
   7.443 +	determine whether the drag-and-drop operation succeeds or not.
   7.444 +
   7.445 +	For objects of version 3 or newer, this request determines the
   7.446 +	final result of the drag-and-drop operation. If the end result
   7.447 +	is that no mime types were accepted, the drag-and-drop operation
   7.448 +	will be cancelled and the corresponding drag source will receive
   7.449 +	wl_data_source.cancelled. Clients may still use this event in
   7.450 +	conjunction with wl_data_source.action for feedback.
   7.451 +      </description>
   7.452 +      <arg name="serial" type="uint" summary="serial number of the accept request"/>
   7.453 +      <arg name="mime_type" type="string" allow-null="true" summary="mime type accepted by the client"/>
   7.454 +    </request>
   7.455 +
   7.456 +    <request name="receive">
   7.457 +      <description summary="request that the data is transferred">
   7.458 +	To transfer the offered data, the client issues this request
   7.459 +	and indicates the mime type it wants to receive.  The transfer
   7.460 +	happens through the passed file descriptor (typically created
   7.461 +	with the pipe system call).  The source client writes the data
   7.462 +	in the mime type representation requested and then closes the
   7.463 +	file descriptor.
   7.464 +
   7.465 +	The receiving client reads from the read end of the pipe until
   7.466 +	EOF and then closes its end, at which point the transfer is
   7.467 +	complete.
   7.468 +
   7.469 +	This request may happen multiple times for different mime types,
   7.470 +	both before and after wl_data_device.drop. Drag-and-drop destination
   7.471 +	clients may preemptively fetch data or examine it more closely to
   7.472 +	determine acceptance.
   7.473 +      </description>
   7.474 +      <arg name="mime_type" type="string" summary="mime type desired by receiver"/>
   7.475 +      <arg name="fd" type="fd" summary="file descriptor for data transfer"/>
   7.476 +    </request>
   7.477 +
   7.478 +    <request name="destroy" type="destructor">
   7.479 +      <description summary="destroy data offer">
   7.480 +	Destroy the data offer.
   7.481 +      </description>
   7.482 +    </request>
   7.483 +
   7.484 +    <event name="offer">
   7.485 +      <description summary="advertise offered mime type">
   7.486 +	Sent immediately after creating the wl_data_offer object.  One
   7.487 +	event per offered mime type.
   7.488 +      </description>
   7.489 +      <arg name="mime_type" type="string" summary="offered mime type"/>
   7.490 +    </event>
   7.491 +
   7.492 +    <!-- Version 3 additions -->
   7.493 +
   7.494 +    <request name="finish" since="3">
   7.495 +      <description summary="the offer will no longer be used">
   7.496 +	Notifies the compositor that the drag destination successfully
   7.497 +	finished the drag-and-drop operation.
   7.498 +
   7.499 +	Upon receiving this request, the compositor will emit
   7.500 +	wl_data_source.dnd_finished on the drag source client.
   7.501 +
   7.502 +	It is a client error to perform other requests than
   7.503 +	wl_data_offer.destroy after this one. It is also an error to perform
   7.504 +	this request after a NULL mime type has been set in
   7.505 +	wl_data_offer.accept or no action was received through
   7.506 +	wl_data_offer.action.
   7.507 +      </description>
   7.508 +    </request>
   7.509 +
   7.510 +    <request name="set_actions" since="3">
   7.511 +      <description summary="set the available/preferred drag-and-drop actions">
   7.512 +	Sets the actions that the destination side client supports for
   7.513 +	this operation. This request may trigger the emission of
   7.514 +	wl_data_source.action and wl_data_offer.action events if the compositor
   7.515 +	needs to change the selected action.
   7.516 +
   7.517 +	This request can be called multiple times throughout the
   7.518 +	drag-and-drop operation, typically in response to wl_data_device.enter
   7.519 +	or wl_data_device.motion events.
   7.520 +
   7.521 +	This request determines the final result of the drag-and-drop
   7.522 +	operation. If the end result is that no action is accepted,
   7.523 +	the drag source will receive wl_drag_source.cancelled.
   7.524 +
   7.525 +	The dnd_actions argument must contain only values expressed in the
   7.526 +	wl_data_device_manager.dnd_actions enum, and the preferred_action
   7.527 +	argument must only contain one of those values set, otherwise it
   7.528 +	will result in a protocol error.
   7.529 +
   7.530 +	While managing an "ask" action, the destination drag-and-drop client
   7.531 +	may perform further wl_data_offer.receive requests, and is expected
   7.532 +	to perform one last wl_data_offer.set_actions request with a preferred
   7.533 +	action other than "ask" (and optionally wl_data_offer.accept) before
   7.534 +	requesting wl_data_offer.finish, in order to convey the action selected
   7.535 +	by the user. If the preferred action is not in the
   7.536 +	wl_data_offer.source_actions mask, an error will be raised.
   7.537 +
   7.538 +	If the "ask" action is dismissed (e.g. user cancellation), the client
   7.539 +	is expected to perform wl_data_offer.destroy right away.
   7.540 +
   7.541 +	This request can only be made on drag-and-drop offers, a protocol error
   7.542 +	will be raised otherwise.
   7.543 +      </description>
   7.544 +      <arg name="dnd_actions" type="uint" summary="actions supported by the destination client"/>
   7.545 +      <arg name="preferred_action" type="uint" summary="action preferred by the destination client"/>
   7.546 +    </request>
   7.547 +
   7.548 +    <event name="source_actions" since="3">
   7.549 +      <description summary="notify the source-side available actions">
   7.550 +	This event indicates the actions offered by the data source. It
   7.551 +	will be sent right after wl_data_device.enter, or anytime the source
   7.552 +	side changes its offered actions through wl_data_source.set_actions.
   7.553 +      </description>
   7.554 +      <arg name="source_actions" type="uint" summary="actions offered by the data source"/>
   7.555 +    </event>
   7.556 +
   7.557 +    <event name="action" since="3">
   7.558 +      <description summary="notify the selected action">
   7.559 +	This event indicates the action selected by the compositor after
   7.560 +	matching the source/destination side actions. Only one action (or
   7.561 +	none) will be offered here.
   7.562 +
   7.563 +	This event can be emitted multiple times during the drag-and-drop
   7.564 +	operation in response to destination side action changes through
   7.565 +	wl_data_offer.set_actions.
   7.566 +
   7.567 +	This event will no longer be emitted after wl_data_device.drop
   7.568 +	happened on the drag-and-drop destination, the client must
   7.569 +	honor the last action received, or the last preferred one set
   7.570 +	through wl_data_offer.set_actions when handling an "ask" action.
   7.571 +
   7.572 +	Compositors may also change the selected action on the fly, mainly
   7.573 +	in response to keyboard modifier changes during the drag-and-drop
   7.574 +	operation.
   7.575 +
   7.576 +	The most recent action received is always the valid one. Prior to
   7.577 +	receiving wl_data_device.drop, the chosen action may change (e.g.
   7.578 +	due to keyboard modifiers being pressed). At the time of receiving
   7.579 +	wl_data_device.drop the drag-and-drop destination must honor the
   7.580 +	last action received.
   7.581 +
   7.582 +	Action changes may still happen after wl_data_device.drop,
   7.583 +	especially on "ask" actions, where the drag-and-drop destination
   7.584 +	may choose another action afterwards. Action changes happening
   7.585 +	at this stage are always the result of inter-client negotiation, the
   7.586 +	compositor shall no longer be able to induce a different action.
   7.587 +
   7.588 +	Upon "ask" actions, it is expected that the drag-and-drop destination
   7.589 +	may potentially choose a different action and/or mime type,
   7.590 +	based on wl_data_offer.source_actions and finally chosen by the
   7.591 +	user (e.g. popping up a menu with the available options). The
   7.592 +	final wl_data_offer.set_actions and wl_data_offer.accept requests
   7.593 +	must happen before the call to wl_data_offer.finish.
   7.594 +      </description>
   7.595 +      <arg name="dnd_action" type="uint" summary="action selected by the compositor"/>
   7.596 +    </event>
   7.597 +  </interface>
   7.598 +
   7.599 +  <interface name="wl_data_source" version="3">
   7.600 +    <description summary="offer to transfer data">
   7.601 +      The wl_data_source object is the source side of a wl_data_offer.
   7.602 +      It is created by the source client in a data transfer and
   7.603 +      provides a way to describe the offered data and a way to respond
   7.604 +      to requests to transfer the data.
   7.605 +    </description>
   7.606 +
   7.607 +    <enum name="error">
   7.608 +      <entry name="invalid_action_mask" value="0"
   7.609 +	     summary="action mask contains invalid values"/>
   7.610 +      <entry name="invalid_source" value="1"
   7.611 +	     summary="source doesn't accept this request"/>
   7.612 +    </enum>
   7.613 +
   7.614 +    <request name="offer">
   7.615 +      <description summary="add an offered mime type">
   7.616 +	This request adds a mime type to the set of mime types
   7.617 +	advertised to targets.  Can be called several times to offer
   7.618 +	multiple types.
   7.619 +      </description>
   7.620 +      <arg name="mime_type" type="string" summary="mime type offered by the data source"/>
   7.621 +    </request>
   7.622 +
   7.623 +    <request name="destroy" type="destructor">
   7.624 +      <description summary="destroy the data source">
   7.625 +	Destroy the data source.
   7.626 +      </description>
   7.627 +    </request>
   7.628 +
   7.629 +    <event name="target">
   7.630 +      <description summary="a target accepts an offered mime type">
   7.631 +	Sent when a target accepts pointer_focus or motion events.  If
   7.632 +	a target does not accept any of the offered types, type is NULL.
   7.633 +
   7.634 +	Used for feedback during drag-and-drop.
   7.635 +      </description>
   7.636 +      <arg name="mime_type" type="string" allow-null="true" summary="mime type accepted by the target"/>
   7.637 +    </event>
   7.638 +
   7.639 +    <event name="send">
   7.640 +      <description summary="send the data">
   7.641 +	Request for data from the client.  Send the data as the
   7.642 +	specified mime type over the passed file descriptor, then
   7.643 +	close it.
   7.644 +      </description>
   7.645 +      <arg name="mime_type" type="string" summary="mime type for the data"/>
   7.646 +      <arg name="fd" type="fd" summary="file descriptor for the data"/>
   7.647 +    </event>
   7.648 +
   7.649 +    <event name="cancelled">
   7.650 +      <description summary="selection was cancelled">
   7.651 +	This data source is no longer valid. There are several reasons why
   7.652 +	this could happen:
   7.653 +
   7.654 +	- The data source has been replaced by another data source.
   7.655 +	- The drag-and-drop operation was performed, but the drop destination
   7.656 +	  did not accept any of the mime types offered through
   7.657 +	  wl_data_source.target.
   7.658 +	- The drag-and-drop operation was performed, but the drop destination
   7.659 +	  did not select any of the actions present in the mask offered through
   7.660 +	  wl_data_source.action.
   7.661 +	- The drag-and-drop operation was performed but didn't happen over a
   7.662 +	  surface.
   7.663 +	- The compositor cancelled the drag-and-drop operation (e.g. compositor
   7.664 +	  dependent timeouts to avoid stale drag-and-drop transfers).
   7.665 +
   7.666 +	The client should clean up and destroy this data source.
   7.667 +
   7.668 +	For objects of version 2 or older, wl_data_source.cancelled will
   7.669 +	only be emitted if the data source was replaced by another data
   7.670 +	source.
   7.671 +      </description>
   7.672 +    </event>
   7.673 +
   7.674 +    <!-- Version 3 additions -->
   7.675 +
   7.676 +    <request name="set_actions" since="3">
   7.677 +      <description summary="set the available drag-and-drop actions">
   7.678 +	Sets the actions that the source side client supports for this
   7.679 +	operation. This request may trigger wl_data_source.action and
   7.680 +	wl_data_offer.action events if the compositor needs to change the
   7.681 +	selected action.
   7.682 +
   7.683 +	The dnd_actions argument must contain only values expressed in the
   7.684 +	wl_data_device_manager.dnd_actions enum, otherwise it will result
   7.685 +	in a protocol error.
   7.686 +
   7.687 +	This request must be made once only, and can only be made on sources
   7.688 +	used in drag-and-drop, so it must be performed before
   7.689 +	wl_data_device.start_drag. Attempting to use the source other than
   7.690 +	for drag-and-drop will raise a protocol error.
   7.691 +      </description>
   7.692 +      <arg name="dnd_actions" type="uint" summary="actions supported by the data source"/>
   7.693 +    </request>
   7.694 +
   7.695 +    <event name="dnd_drop_performed" since="3">
   7.696 +      <description summary="the drag-and-drop operation physically finished">
   7.697 +	The user performed the drop action. This event does not indicate
   7.698 +	acceptance, wl_data_source.cancelled may still be emitted afterwards
   7.699 +	if the drop destination does not accept any mime type.
   7.700 +
   7.701 +	However, this event might however not be received if the compositor
   7.702 +	cancelled the drag-and-drop operation before this event could happen.
   7.703 +
   7.704 +	Note that the data_source may still be used in the future and should
   7.705 +	not be destroyed here.
   7.706 +      </description>
   7.707 +    </event>
   7.708 +
   7.709 +    <event name="dnd_finished" since="3">
   7.710 +      <description summary="the drag-and-drop operation concluded">
   7.711 +	The drop destination finished interoperating with this data
   7.712 +	source, so the client is now free to destroy this data source and
   7.713 +	free all associated data.
   7.714 +
   7.715 +	If the action used to perform the operation was "move", the
   7.716 +	source can now delete the transferred data.
   7.717 +      </description>
   7.718 +    </event>
   7.719 +
   7.720 +    <event name="action" since="3">
   7.721 +      <description summary="notify the selected action">
   7.722 +	This event indicates the action selected by the compositor after
   7.723 +	matching the source/destination side actions. Only one action (or
   7.724 +	none) will be offered here.
   7.725 +
   7.726 +	This event can be emitted multiple times during the drag-and-drop
   7.727 +	operation, mainly in response to destination side changes through
   7.728 +	wl_data_offer.set_actions, and as the data device enters/leaves
   7.729 +	surfaces.
   7.730 +
   7.731 +	It is only possible to receive this event after
   7.732 +	wl_data_source.dnd_drop_performed if the drag-and-drop operation
   7.733 +	ended in an "ask" action, in which case the final wl_data_source.action
   7.734 +	event will happen immediately before wl_data_source.dnd_finished.
   7.735 +
   7.736 +	Compositors may also change the selected action on the fly, mainly
   7.737 +	in response to keyboard modifier changes during the drag-and-drop
   7.738 +	operation.
   7.739 +
   7.740 +	The most recent action received is always the valid one. The chosen
   7.741 +	action may change alongside negotiation (e.g. an "ask" action can turn
   7.742 +	into a "move" operation), so the effects of the final action must
   7.743 +	always be applied in wl_data_offer.dnd_finished.
   7.744 +
   7.745 +	Clients can trigger cursor surface changes from this point, so
   7.746 +	they reflect the current action.
   7.747 +      </description>
   7.748 +      <arg name="dnd_action" type="uint" summary="action selected by the compositor"/>
   7.749 +    </event>
   7.750 +  </interface>
   7.751 +
   7.752 +  <interface name="wl_data_device" version="3">
   7.753 +    <description summary="data transfer device">
   7.754 +      There is one wl_data_device per seat which can be obtained
   7.755 +      from the global wl_data_device_manager singleton.
   7.756 +
   7.757 +      A wl_data_device provides access to inter-client data transfer
   7.758 +      mechanisms such as copy-and-paste and drag-and-drop.
   7.759 +    </description>
   7.760 +
   7.761 +    <enum name="error">
   7.762 +      <entry name="role" value="0" summary="given wl_surface has another role"/>
   7.763 +    </enum>
   7.764 +
   7.765 +    <request name="start_drag">
   7.766 +      <description summary="start drag-and-drop operation">
   7.767 +	This request asks the compositor to start a drag-and-drop
   7.768 +	operation on behalf of the client.
   7.769 +
   7.770 +	The source argument is the data source that provides the data
   7.771 +	for the eventual data transfer. If source is NULL, enter, leave
   7.772 +	and motion events are sent only to the client that initiated the
   7.773 +	drag and the client is expected to handle the data passing
   7.774 +	internally.
   7.775 +
   7.776 +	The origin surface is the surface where the drag originates and
   7.777 +	the client must have an active implicit grab that matches the
   7.778 +	serial.
   7.779 +
   7.780 +	The icon surface is an optional (can be NULL) surface that
   7.781 +	provides an icon to be moved around with the cursor.  Initially,
   7.782 +	the top-left corner of the icon surface is placed at the cursor
   7.783 +	hotspot, but subsequent wl_surface.attach request can move the
   7.784 +	relative position. Attach requests must be confirmed with
   7.785 +	wl_surface.commit as usual. The icon surface is given the role of
   7.786 +	a drag-and-drop icon. If the icon surface already has another role,
   7.787 +	it raises a protocol error.
   7.788 +
   7.789 +	The current and pending input regions of the icon wl_surface are
   7.790 +	cleared, and wl_surface.set_input_region is ignored until the
   7.791 +	wl_surface is no longer used as the icon surface. When the use
   7.792 +	as an icon ends, the current and pending input regions become
   7.793 +	undefined, and the wl_surface is unmapped.
   7.794 +      </description>
   7.795 +      <arg name="source" type="object" interface="wl_data_source" allow-null="true" summary="data source for the eventual transfer"/>
   7.796 +      <arg name="origin" type="object" interface="wl_surface" summary="surface where the drag originates"/>
   7.797 +      <arg name="icon" type="object" interface="wl_surface" allow-null="true" summary="drag-and-drop icon surface"/>
   7.798 +      <arg name="serial" type="uint" summary="serial number of the implicit grab on the origin"/>
   7.799 +    </request>
   7.800 +
   7.801 +    <request name="set_selection">
   7.802 +      <description summary="copy data to the selection">
   7.803 +	This request asks the compositor to set the selection
   7.804 +	to the data from the source on behalf of the client.
   7.805 +
   7.806 +	To unset the selection, set the source to NULL.
   7.807 +      </description>
   7.808 +      <arg name="source" type="object" interface="wl_data_source" allow-null="true" summary="data source for the selection"/>
   7.809 +      <arg name="serial" type="uint" summary="serial number of the event that triggered this request"/>
   7.810 +    </request>
   7.811 +
   7.812 +    <event name="data_offer">
   7.813 +      <description summary="introduce a new wl_data_offer">
   7.814 +	The data_offer event introduces a new wl_data_offer object,
   7.815 +	which will subsequently be used in either the
   7.816 +	data_device.enter event (for drag-and-drop) or the
   7.817 +	data_device.selection event (for selections).  Immediately
   7.818 +	following the data_device_data_offer event, the new data_offer
   7.819 +	object will send out data_offer.offer events to describe the
   7.820 +	mime types it offers.
   7.821 +      </description>
   7.822 +      <arg name="id" type="new_id" interface="wl_data_offer" summary="the new data_offer object"/>
   7.823 +    </event>
   7.824 +
   7.825 +    <event name="enter">
   7.826 +      <description summary="initiate drag-and-drop session">
   7.827 +	This event is sent when an active drag-and-drop pointer enters
   7.828 +	a surface owned by the client.  The position of the pointer at
   7.829 +	enter time is provided by the x and y arguments, in surface-local
   7.830 +	coordinates.
   7.831 +      </description>
   7.832 +      <arg name="serial" type="uint" summary="serial number of the enter event"/>
   7.833 +      <arg name="surface" type="object" interface="wl_surface" summary="client surface entered"/>
   7.834 +      <arg name="x" type="fixed" summary="surface-local x coordinate"/>
   7.835 +      <arg name="y" type="fixed" summary="surface-local y coordinate"/>
   7.836 +      <arg name="id" type="object" interface="wl_data_offer" allow-null="true"
   7.837 +	   summary="source data_offer object"/>
   7.838 +    </event>
   7.839 +
   7.840 +    <event name="leave">
   7.841 +      <description summary="end drag-and-drop session">
   7.842 +	This event is sent when the drag-and-drop pointer leaves the
   7.843 +	surface and the session ends.  The client must destroy the
   7.844 +	wl_data_offer introduced at enter time at this point.
   7.845 +      </description>
   7.846 +    </event>
   7.847 +
   7.848 +    <event name="motion">
   7.849 +      <description summary="drag-and-drop session motion">
   7.850 +	This event is sent when the drag-and-drop pointer moves within
   7.851 +	the currently focused surface. The new position of the pointer
   7.852 +	is provided by the x and y arguments, in surface-local
   7.853 +	coordinates.
   7.854 +      </description>
   7.855 +      <arg name="time" type="uint" summary="timestamp with millisecond granularity"/>
   7.856 +      <arg name="x" type="fixed" summary="surface-local x coordinate"/>
   7.857 +      <arg name="y" type="fixed" summary="surface-local y coordinate"/>
   7.858 +    </event>
   7.859 +
   7.860 +    <event name="drop">
   7.861 +      <description summary="end drag-and-drop session successfully">
   7.862 +	The event is sent when a drag-and-drop operation is ended
   7.863 +	because the implicit grab is removed.
   7.864 +
   7.865 +	The drag-and-drop destination is expected to honor the last action
   7.866 +	received through wl_data_offer.action, if the resulting action is
   7.867 +	"copy" or "move", the destination can still perform
   7.868 +	wl_data_offer.receive requests, and is expected to end all
   7.869 +	transfers with a wl_data_offer.finish request.
   7.870 +
   7.871 +	If the resulting action is "ask", the action will not be considered
   7.872 +	final. The drag-and-drop destination is expected to perform one last
   7.873 +	wl_data_offer.set_actions request, or wl_data_offer.destroy in order
   7.874 +	to cancel the operation.
   7.875 +      </description>
   7.876 +    </event>
   7.877 +
   7.878 +    <event name="selection">
   7.879 +      <description summary="advertise new selection">
   7.880 +	The selection event is sent out to notify the client of a new
   7.881 +	wl_data_offer for the selection for this device.  The
   7.882 +	data_device.data_offer and the data_offer.offer events are
   7.883 +	sent out immediately before this event to introduce the data
   7.884 +	offer object.  The selection event is sent to a client
   7.885 +	immediately before receiving keyboard focus and when a new
   7.886 +	selection is set while the client has keyboard focus.  The
   7.887 +	data_offer is valid until a new data_offer or NULL is received
   7.888 +	or until the client loses keyboard focus.  The client must
   7.889 +	destroy the previous selection data_offer, if any, upon receiving
   7.890 +	this event.
   7.891 +      </description>
   7.892 +      <arg name="id" type="object" interface="wl_data_offer" allow-null="true"
   7.893 +	   summary="selection data_offer object"/>
   7.894 +    </event>
   7.895 +
   7.896 +    <!-- Version 2 additions -->
   7.897 +
   7.898 +    <request name="release" type="destructor" since="2">
   7.899 +      <description summary="destroy data device">
   7.900 +	This request destroys the data device.
   7.901 +      </description>
   7.902 +    </request>
   7.903 +  </interface>
   7.904 +
   7.905 +  <interface name="wl_data_device_manager" version="3">
   7.906 +    <description summary="data transfer interface">
   7.907 +      The wl_data_device_manager is a singleton global object that
   7.908 +      provides access to inter-client data transfer mechanisms such as
   7.909 +      copy-and-paste and drag-and-drop.  These mechanisms are tied to
   7.910 +      a wl_seat and this interface lets a client get a wl_data_device
   7.911 +      corresponding to a wl_seat.
   7.912 +
   7.913 +      Depending on the version bound, the objects created from the bound
   7.914 +      wl_data_device_manager object will have different requirements for
   7.915 +      functioning properly. See wl_data_source.set_actions,
   7.916 +      wl_data_offer.accept and wl_data_offer.finish for details.
   7.917 +    </description>
   7.918 +
   7.919 +    <request name="create_data_source">
   7.920 +      <description summary="create a new data source">
   7.921 +	Create a new data source.
   7.922 +      </description>
   7.923 +      <arg name="id" type="new_id" interface="wl_data_source" summary="data source to create"/>
   7.924 +    </request>
   7.925 +
   7.926 +    <request name="get_data_device">
   7.927 +      <description summary="create a new data device">
   7.928 +	Create a new data device for a given seat.
   7.929 +      </description>
   7.930 +      <arg name="id" type="new_id" interface="wl_data_device" summary="data device to create"/>
   7.931 +      <arg name="seat" type="object" interface="wl_seat" summary="seat associated with the data device"/>
   7.932 +    </request>
   7.933 +
   7.934 +    <!-- Version 3 additions -->
   7.935 +
   7.936 +    <enum name="dnd_action" bitfield="true" since="3">
   7.937 +      <description summary="drag and drop actions">
   7.938 +	This is a bitmask of the available/preferred actions in a
   7.939 +	drag-and-drop operation.
   7.940 +
   7.941 +	In the compositor, the selected action is a result of matching the
   7.942 +	actions offered by the source and destination sides.  "action" events
   7.943 +	with a "none" action will be sent to both source and destination if
   7.944 +	there is no match. All further checks will effectively happen on
   7.945 +	(source actions ∩ destination actions).
   7.946 +
   7.947 +	In addition, compositors may also pick different actions in
   7.948 +	reaction to key modifiers being pressed. One common design that
   7.949 +	is used in major toolkits (and the behavior recommended for
   7.950 +	compositors) is:
   7.951 +
   7.952 +	- If no modifiers are pressed, the first match (in bit order)
   7.953 +	  will be used.
   7.954 +	- Pressing Shift selects "move", if enabled in the mask.
   7.955 +	- Pressing Control selects "copy", if enabled in the mask.
   7.956 +
   7.957 +	Behavior beyond that is considered implementation-dependent.
   7.958 +	Compositors may for example bind other modifiers (like Alt/Meta)
   7.959 +	or drags initiated with other buttons than BTN_LEFT to specific
   7.960 +	actions (e.g. "ask").
   7.961 +      </description>
   7.962 +      <entry name="none" value="0" summary="no action"/>
   7.963 +      <entry name="copy" value="1" summary="copy action"/>
   7.964 +      <entry name="move" value="2" summary="move action"/>
   7.965 +      <entry name="ask" value="4" summary="ask action"/>
   7.966 +    </enum>
   7.967 +  </interface>
   7.968 +
   7.969 +  <interface name="wl_shell" version="1">
   7.970 +    <description summary="create desktop-style surfaces">
   7.971 +      This interface is implemented by servers that provide
   7.972 +      desktop-style user interfaces.
   7.973 +
   7.974 +      It allows clients to associate a wl_shell_surface with
   7.975 +      a basic surface.
   7.976 +    </description>
   7.977 +
   7.978 +    <enum name="error">
   7.979 +      <entry name="role" value="0" summary="given wl_surface has another role"/>
   7.980 +    </enum>
   7.981 +
   7.982 +    <request name="get_shell_surface">
   7.983 +      <description summary="create a shell surface from a surface">
   7.984 +	Create a shell surface for an existing surface. This gives
   7.985 +	the wl_surface the role of a shell surface. If the wl_surface
   7.986 +	already has another role, it raises a protocol error.
   7.987 +
   7.988 +	Only one shell surface can be associated with a given surface.
   7.989 +      </description>
   7.990 +      <arg name="id" type="new_id" interface="wl_shell_surface" summary="shell surface to create"/>
   7.991 +      <arg name="surface" type="object" interface="wl_surface" summary="surface to be given the shell surface role"/>
   7.992 +    </request>
   7.993 +  </interface>
   7.994 +
   7.995 +  <interface name="wl_shell_surface" version="1">
   7.996 +    <description summary="desktop-style metadata interface">
   7.997 +      An interface that may be implemented by a wl_surface, for
   7.998 +      implementations that provide a desktop-style user interface.
   7.999 +
  7.1000 +      It provides requests to treat surfaces like toplevel, fullscreen
  7.1001 +      or popup windows, move, resize or maximize them, associate
  7.1002 +      metadata like title and class, etc.
  7.1003 +
  7.1004 +      On the server side the object is automatically destroyed when
  7.1005 +      the related wl_surface is destroyed. On the client side,
  7.1006 +      wl_shell_surface_destroy() must be called before destroying
  7.1007 +      the wl_surface object.
  7.1008 +    </description>
  7.1009 +
  7.1010 +    <request name="pong">
  7.1011 +      <description summary="respond to a ping event">
  7.1012 +	A client must respond to a ping event with a pong request or
  7.1013 +	the client may be deemed unresponsive.
  7.1014 +      </description>
  7.1015 +      <arg name="serial" type="uint" summary="serial number of the ping event"/>
  7.1016 +    </request>
  7.1017 +
  7.1018 +    <request name="move">
  7.1019 +      <description summary="start an interactive move">
  7.1020 +	Start a pointer-driven move of the surface.
  7.1021 +
  7.1022 +	This request must be used in response to a button press event.
  7.1023 +	The server may ignore move requests depending on the state of
  7.1024 +	the surface (e.g. fullscreen or maximized).
  7.1025 +      </description>
  7.1026 +      <arg name="seat" type="object" interface="wl_seat" summary="seat whose pointer is used"/>
  7.1027 +      <arg name="serial" type="uint" summary="serial number of the implicit grab on the pointer"/>
  7.1028 +    </request>
  7.1029 +
  7.1030 +    <enum name="resize" bitfield="true">
  7.1031 +      <description summary="edge values for resizing">
  7.1032 +	These values are used to indicate which edge of a surface
  7.1033 +	is being dragged in a resize operation. The server may
  7.1034 +	use this information to adapt its behavior, e.g. choose
  7.1035 +	an appropriate cursor image.
  7.1036 +      </description>
  7.1037 +      <entry name="none" value="0" summary="no edge"/>
  7.1038 +      <entry name="top" value="1" summary="top edge"/>
  7.1039 +      <entry name="bottom" value="2" summary="bottom edge"/>
  7.1040 +      <entry name="left" value="4" summary="left edge"/>
  7.1041 +      <entry name="top_left" value="5" summary="top and left edges"/>
  7.1042 +      <entry name="bottom_left" value="6" summary="bottom and left edges"/>
  7.1043 +      <entry name="right" value="8" summary="right edge"/>
  7.1044 +      <entry name="top_right" value="9" summary="top and right edges"/>
  7.1045 +      <entry name="bottom_right" value="10" summary="bottom and right edges"/>
  7.1046 +    </enum>
  7.1047 +
  7.1048 +    <request name="resize">
  7.1049 +      <description summary="start an interactive resize">
  7.1050 +	Start a pointer-driven resizing of the surface.
  7.1051 +
  7.1052 +	This request must be used in response to a button press event.
  7.1053 +	The server may ignore resize requests depending on the state of
  7.1054 +	the surface (e.g. fullscreen or maximized).
  7.1055 +      </description>
  7.1056 +      <arg name="seat" type="object" interface="wl_seat" summary="seat whose pointer is used"/>
  7.1057 +      <arg name="serial" type="uint" summary="serial number of the implicit grab on the pointer"/>
  7.1058 +      <arg name="edges" type="uint" enum="resize" summary="which edge or corner is being dragged"/>
  7.1059 +    </request>
  7.1060 +
  7.1061 +    <request name="set_toplevel">
  7.1062 +      <description summary="make the surface a toplevel surface">
  7.1063 +	Map the surface as a toplevel surface.
  7.1064 +
  7.1065 +	A toplevel surface is not fullscreen, maximized or transient.
  7.1066 +      </description>
  7.1067 +    </request>
  7.1068 +
  7.1069 +    <enum name="transient" bitfield="true">
  7.1070 +      <description summary="details of transient behaviour">
  7.1071 +	These flags specify details of the expected behaviour
  7.1072 +	of transient surfaces. Used in the set_transient request.
  7.1073 +      </description>
  7.1074 +      <entry name="inactive" value="0x1" summary="do not set keyboard focus"/>
  7.1075 +    </enum>
  7.1076 +
  7.1077 +    <request name="set_transient">
  7.1078 +      <description summary="make the surface a transient surface">
  7.1079 +	Map the surface relative to an existing surface.
  7.1080 +
  7.1081 +	The x and y arguments specify the location of the upper left
  7.1082 +	corner of the surface relative to the upper left corner of the
  7.1083 +	parent surface, in surface-local coordinates.
  7.1084 +
  7.1085 +	The flags argument controls details of the transient behaviour.
  7.1086 +      </description>
  7.1087 +      <arg name="parent" type="object" interface="wl_surface" summary="parent surface"/>
  7.1088 +      <arg name="x" type="int" summary="surface-local x coordinate"/>
  7.1089 +      <arg name="y" type="int" summary="surface-local y coordinate"/>
  7.1090 +      <arg name="flags" type="uint" enum="transient" summary="transient surface behavior"/>
  7.1091 +    </request>
  7.1092 +
  7.1093 +    <enum name="fullscreen_method">
  7.1094 +      <description summary="different method to set the surface fullscreen">
  7.1095 +	Hints to indicate to the compositor how to deal with a conflict
  7.1096 +	between the dimensions of the surface and the dimensions of the
  7.1097 +	output. The compositor is free to ignore this parameter.
  7.1098 +      </description>
  7.1099 +      <entry name="default" value="0" summary="no preference, apply default policy"/>
  7.1100 +      <entry name="scale" value="1" summary="scale, preserve the surface's aspect ratio and center on output"/>
  7.1101 +      <entry name="driver" value="2" summary="switch output mode to the smallest mode that can fit the surface, add black borders to compensate size mismatch"/>
  7.1102 +      <entry name="fill" value="3" summary="no upscaling, center on output and add black borders to compensate size mismatch"/>
  7.1103 +    </enum>
  7.1104 +
  7.1105 +    <request name="set_fullscreen">
  7.1106 +      <description summary="make the surface a fullscreen surface">
  7.1107 +	Map the surface as a fullscreen surface.
  7.1108 +
  7.1109 +	If an output parameter is given then the surface will be made
  7.1110 +	fullscreen on that output. If the client does not specify the
  7.1111 +	output then the compositor will apply its policy - usually
  7.1112 +	choosing the output on which the surface has the biggest surface
  7.1113 +	area.
  7.1114 +
  7.1115 +	The client may specify a method to resolve a size conflict
  7.1116 +	between the output size and the surface size - this is provided
  7.1117 +	through the method parameter.
  7.1118 +
  7.1119 +	The framerate parameter is used only when the method is set
  7.1120 +	to "driver", to indicate the preferred framerate. A value of 0
  7.1121 +	indicates that the client does not care about framerate.  The
  7.1122 +	framerate is specified in mHz, that is framerate of 60000 is 60Hz.
  7.1123 +
  7.1124 +	A method of "scale" or "driver" implies a scaling operation of
  7.1125 +	the surface, either via a direct scaling operation or a change of
  7.1126 +	the output mode. This will override any kind of output scaling, so
  7.1127 +	that mapping a surface with a buffer size equal to the mode can
  7.1128 +	fill the screen independent of buffer_scale.
  7.1129 +
  7.1130 +	A method of "fill" means we don't scale up the buffer, however
  7.1131 +	any output scale is applied. This means that you may run into
  7.1132 +	an edge case where the application maps a buffer with the same
  7.1133 +	size of the output mode but buffer_scale 1 (thus making a
  7.1134 +	surface larger than the output). In this case it is allowed to
  7.1135 +	downscale the results to fit the screen.
  7.1136 +
  7.1137 +	The compositor must reply to this request with a configure event
  7.1138 +	with the dimensions for the output on which the surface will
  7.1139 +	be made fullscreen.
  7.1140 +      </description>
  7.1141 +      <arg name="method" type="uint" enum="fullscreen_method" summary="method for resolving size conflict"/>
  7.1142 +      <arg name="framerate" type="uint" summary="framerate in mHz"/>
  7.1143 +      <arg name="output" type="object" interface="wl_output" allow-null="true"
  7.1144 +	   summary="output on which the surface is to be fullscreen"/>
  7.1145 +    </request>
  7.1146 +
  7.1147 +    <request name="set_popup">
  7.1148 +      <description summary="make the surface a popup surface">
  7.1149 +	Map the surface as a popup.
  7.1150 +
  7.1151 +	A popup surface is a transient surface with an added pointer
  7.1152 +	grab.
  7.1153 +
  7.1154 +	An existing implicit grab will be changed to owner-events mode,
  7.1155 +	and the popup grab will continue after the implicit grab ends
  7.1156 +	(i.e. releasing the mouse button does not cause the popup to
  7.1157 +	be unmapped).
  7.1158 +
  7.1159 +	The popup grab continues until the window is destroyed or a
  7.1160 +	mouse button is pressed in any other client's window. A click
  7.1161 +	in any of the client's surfaces is reported as normal, however,
  7.1162 +	clicks in other clients' surfaces will be discarded and trigger
  7.1163 +	the callback.
  7.1164 +
  7.1165 +	The x and y arguments specify the location of the upper left
  7.1166 +	corner of the surface relative to the upper left corner of the
  7.1167 +	parent surface, in surface-local coordinates.
  7.1168 +      </description>
  7.1169 +      <arg name="seat" type="object" interface="wl_seat" summary="seat whose pointer is used"/>
  7.1170 +      <arg name="serial" type="uint" summary="serial number of the implicit grab on the pointer"/>
  7.1171 +      <arg name="parent" type="object" interface="wl_surface" summary="parent surface"/>
  7.1172 +      <arg name="x" type="int" summary="surface-local x coordinate"/>
  7.1173 +      <arg name="y" type="int" summary="surface-local y coordinate"/>
  7.1174 +      <arg name="flags" type="uint" enum="transient" summary="transient surface behavior"/>
  7.1175 +    </request>
  7.1176 +
  7.1177 +    <request name="set_maximized">
  7.1178 +      <description summary="make the surface a maximized surface">
  7.1179 +	Map the surface as a maximized surface.
  7.1180 +
  7.1181 +	If an output parameter is given then the surface will be
  7.1182 +	maximized on that output. If the client does not specify the
  7.1183 +	output then the compositor will apply its policy - usually
  7.1184 +	choosing the output on which the surface has the biggest surface
  7.1185 +	area.
  7.1186 +
  7.1187 +	The compositor will reply with a configure event telling
  7.1188 +	the expected new surface size. The operation is completed
  7.1189 +	on the next buffer attach to this surface.
  7.1190 +
  7.1191 +	A maximized surface typically fills the entire output it is
  7.1192 +	bound to, except for desktop elements such as panels. This is
  7.1193 +	the main difference between a maximized shell surface and a
  7.1194 +	fullscreen shell surface.
  7.1195 +
  7.1196 +	The details depend on the compositor implementation.
  7.1197 +      </description>
  7.1198 +      <arg name="output" type="object" interface="wl_output" allow-null="true"
  7.1199 +	   summary="output on which the surface is to be maximized"/>
  7.1200 +    </request>
  7.1201 +
  7.1202 +    <request name="set_title">
  7.1203 +      <description summary="set surface title">
  7.1204 +	Set a short title for the surface.
  7.1205 +
  7.1206 +	This string may be used to identify the surface in a task bar,
  7.1207 +	window list, or other user interface elements provided by the
  7.1208 +	compositor.
  7.1209 +
  7.1210 +	The string must be encoded in UTF-8.
  7.1211 +      </description>
  7.1212 +      <arg name="title" type="string" summary="surface title"/>
  7.1213 +    </request>
  7.1214 +
  7.1215 +    <request name="set_class">
  7.1216 +      <description summary="set surface class">
  7.1217 +	Set a class for the surface.
  7.1218 +
  7.1219 +	The surface class identifies the general class of applications
  7.1220 +	to which the surface belongs. A common convention is to use the
  7.1221 +	file name (or the full path if it is a non-standard location) of
  7.1222 +	the application's .desktop file as the class.
  7.1223 +      </description>
  7.1224 +      <arg name="class_" type="string" summary="surface class"/>
  7.1225 +    </request>
  7.1226 +
  7.1227 +    <event name="ping">
  7.1228 +      <description summary="ping client">
  7.1229 +	Ping a client to check if it is receiving events and sending
  7.1230 +	requests. A client is expected to reply with a pong request.
  7.1231 +      </description>
  7.1232 +      <arg name="serial" type="uint" summary="serial number of the ping"/>
  7.1233 +    </event>
  7.1234 +
  7.1235 +    <event name="configure">
  7.1236 +      <description summary="suggest resize">
  7.1237 +	The configure event asks the client to resize its surface.
  7.1238 +
  7.1239 +	The size is a hint, in the sense that the client is free to
  7.1240 +	ignore it if it doesn't resize, pick a smaller size (to
  7.1241 +	satisfy aspect ratio or resize in steps of NxM pixels).
  7.1242 +
  7.1243 +	The edges parameter provides a hint about how the surface
  7.1244 +	was resized. The client may use this information to decide
  7.1245 +	how to adjust its content to the new size (e.g. a scrolling
  7.1246 +	area might adjust its content position to leave the viewable
  7.1247 +	content unmoved).
  7.1248 +
  7.1249 +	The client is free to dismiss all but the last configure
  7.1250 +	event it received.
  7.1251 +
  7.1252 +	The width and height arguments specify the size of the window
  7.1253 +	in surface-local coordinates.
  7.1254 +      </description>
  7.1255 +      <arg name="edges" type="uint" enum="resize" summary="how the surface was resized"/>
  7.1256 +      <arg name="width" type="int" summary="new width of the surface"/>
  7.1257 +      <arg name="height" type="int" summary="new height of the surface"/>
  7.1258 +    </event>
  7.1259 +
  7.1260 +    <event name="popup_done">
  7.1261 +      <description summary="popup interaction is done">
  7.1262 +	The popup_done event is sent out when a popup grab is broken,
  7.1263 +	that is, when the user clicks a surface that doesn't belong
  7.1264 +	to the client owning the popup surface.
  7.1265 +      </description>
  7.1266 +    </event>
  7.1267 +  </interface>
  7.1268 +
  7.1269 +  <interface name="wl_surface" version="4">
  7.1270 +    <description summary="an onscreen surface">
  7.1271 +      A surface is a rectangular area that is displayed on the screen.
  7.1272 +      It has a location, size and pixel contents.
  7.1273 +
  7.1274 +      The size of a surface (and relative positions on it) is described
  7.1275 +      in surface-local coordinates, which may differ from the buffer
  7.1276 +      coordinates of the pixel content, in case a buffer_transform
  7.1277 +      or a buffer_scale is used.
  7.1278 +
  7.1279 +      A surface without a "role" is fairly useless: a compositor does
  7.1280 +      not know where, when or how to present it. The role is the
  7.1281 +      purpose of a wl_surface. Examples of roles are a cursor for a
  7.1282 +      pointer (as set by wl_pointer.set_cursor), a drag icon
  7.1283 +      (wl_data_device.start_drag), a sub-surface
  7.1284 +      (wl_subcompositor.get_subsurface), and a window as defined by a
  7.1285 +      shell protocol (e.g. wl_shell.get_shell_surface).
  7.1286 +
  7.1287 +      A surface can have only one role at a time. Initially a
  7.1288 +      wl_surface does not have a role. Once a wl_surface is given a
  7.1289 +      role, it is set permanently for the whole lifetime of the
  7.1290 +      wl_surface object. Giving the current role again is allowed,
  7.1291 +      unless explicitly forbidden by the relevant interface
  7.1292 +      specification.
  7.1293 +
  7.1294 +      Surface roles are given by requests in other interfaces such as
  7.1295 +      wl_pointer.set_cursor. The request should explicitly mention
  7.1296 +      that this request gives a role to a wl_surface. Often, this
  7.1297 +      request also creates a new protocol object that represents the
  7.1298 +      role and adds additional functionality to wl_surface. When a
  7.1299 +      client wants to destroy a wl_surface, they must destroy this 'role
  7.1300 +      object' before the wl_surface.
  7.1301 +
  7.1302 +      Destroying the role object does not remove the role from the
  7.1303 +      wl_surface, but it may stop the wl_surface from "playing the role".
  7.1304 +      For instance, if a wl_subsurface object is destroyed, the wl_surface
  7.1305 +      it was created for will be unmapped and forget its position and
  7.1306 +      z-order. It is allowed to create a wl_subsurface for the same
  7.1307 +      wl_surface again, but it is not allowed to use the wl_surface as
  7.1308 +      a cursor (cursor is a different role than sub-surface, and role
  7.1309 +      switching is not allowed).
  7.1310 +    </description>
  7.1311 +
  7.1312 +    <enum name="error">
  7.1313 +      <description summary="wl_surface error values">
  7.1314 +	These errors can be emitted in response to wl_surface requests.
  7.1315 +      </description>
  7.1316 +      <entry name="invalid_scale" value="0" summary="buffer scale value is invalid"/>
  7.1317 +      <entry name="invalid_transform" value="1" summary="buffer transform value is invalid"/>
  7.1318 +    </enum>
  7.1319 +
  7.1320 +    <request name="destroy" type="destructor">
  7.1321 +      <description summary="delete surface">
  7.1322 +	Deletes the surface and invalidates its object ID.
  7.1323 +      </description>
  7.1324 +    </request>
  7.1325 +
  7.1326 +    <request name="attach">
  7.1327 +      <description summary="set the surface contents">
  7.1328 +	Set a buffer as the content of this surface.
  7.1329 +
  7.1330 +	The new size of the surface is calculated based on the buffer
  7.1331 +	size transformed by the inverse buffer_transform and the
  7.1332 +	inverse buffer_scale. This means that the supplied buffer
  7.1333 +	must be an integer multiple of the buffer_scale.
  7.1334 +
  7.1335 +	The x and y arguments specify the location of the new pending
  7.1336 +	buffer's upper left corner, relative to the current buffer's upper
  7.1337 +	left corner, in surface-local coordinates. In other words, the
  7.1338 +	x and y, combined with the new surface size define in which
  7.1339 +	directions the surface's size changes.
  7.1340 +
  7.1341 +	Surface contents are double-buffered state, see wl_surface.commit.
  7.1342 +
  7.1343 +	The initial surface contents are void; there is no content.
  7.1344 +	wl_surface.attach assigns the given wl_buffer as the pending
  7.1345 +	wl_buffer. wl_surface.commit makes the pending wl_buffer the new
  7.1346 +	surface contents, and the size of the surface becomes the size
  7.1347 +	calculated from the wl_buffer, as described above. After commit,
  7.1348 +	there is no pending buffer until the next attach.
  7.1349 +
  7.1350 +	Committing a pending wl_buffer allows the compositor to read the
  7.1351 +	pixels in the wl_buffer. The compositor may access the pixels at
  7.1352 +	any time after the wl_surface.commit request. When the compositor
  7.1353 +	will not access the pixels anymore, it will send the
  7.1354 +	wl_buffer.release event. Only after receiving wl_buffer.release,
  7.1355 +	the client may reuse the wl_buffer. A wl_buffer that has been
  7.1356 +	attached and then replaced by another attach instead of committed
  7.1357 +	will not receive a release event, and is not used by the
  7.1358 +	compositor.
  7.1359 +
  7.1360 +	Destroying the wl_buffer after wl_buffer.release does not change
  7.1361 +	the surface contents. However, if the client destroys the
  7.1362 +	wl_buffer before receiving the wl_buffer.release event, the surface
  7.1363 +	contents become undefined immediately.
  7.1364 +
  7.1365 +	If wl_surface.attach is sent with a NULL wl_buffer, the
  7.1366 +	following wl_surface.commit will remove the surface content.
  7.1367 +      </description>
  7.1368 +      <arg name="buffer" type="object" interface="wl_buffer" allow-null="true"
  7.1369 +	   summary="buffer of surface contents"/>
  7.1370 +      <arg name="x" type="int" summary="surface-local x coordinate"/>
  7.1371 +      <arg name="y" type="int" summary="surface-local y coordinate"/>
  7.1372 +    </request>
  7.1373 +
  7.1374 +    <request name="damage">
  7.1375 +      <description summary="mark part of the surface damaged">
  7.1376 +	This request is used to describe the regions where the pending
  7.1377 +	buffer is different from the current surface contents, and where
  7.1378 +	the surface therefore needs to be repainted. The compositor
  7.1379 +	ignores the parts of the damage that fall outside of the surface.
  7.1380 +
  7.1381 +	Damage is double-buffered state, see wl_surface.commit.
  7.1382 +
  7.1383 +	The damage rectangle is specified in surface-local coordinates,
  7.1384 +	where x and y specify the upper left corner of the damage rectangle.
  7.1385 +
  7.1386 +	The initial value for pending damage is empty: no damage.
  7.1387 +	wl_surface.damage adds pending damage: the new pending damage
  7.1388 +	is the union of old pending damage and the given rectangle.
  7.1389 +
  7.1390 +	wl_surface.commit assigns pending damage as the current damage,
  7.1391 +	and clears pending damage. The server will clear the current
  7.1392 +	damage as it repaints the surface.
  7.1393 +
  7.1394 +	Alternatively, damage can be posted with wl_surface.damage_buffer
  7.1395 +	which uses buffer coordinates instead of surface coordinates,
  7.1396 +	and is probably the preferred and intuitive way of doing this.
  7.1397 +      </description>
  7.1398 +      <arg name="x" type="int" summary="surface-local x coordinate"/>
  7.1399 +      <arg name="y" type="int" summary="surface-local y coordinate"/>
  7.1400 +      <arg name="width" type="int" summary="width of damage rectangle"/>
  7.1401 +      <arg name="height" type="int" summary="height of damage rectangle"/>
  7.1402 +    </request>
  7.1403 +
  7.1404 +    <request name="frame">
  7.1405 +      <description summary="request a frame throttling hint">
  7.1406 +	Request a notification when it is a good time to start drawing a new
  7.1407 +	frame, by creating a frame callback. This is useful for throttling
  7.1408 +	redrawing operations, and driving animations.
  7.1409 +
  7.1410 +	When a client is animating on a wl_surface, it can use the 'frame'
  7.1411 +	request to get notified when it is a good time to draw and commit the
  7.1412 +	next frame of animation. If the client commits an update earlier than
  7.1413 +	that, it is likely that some updates will not make it to the display,
  7.1414 +	and the client is wasting resources by drawing too often.
  7.1415 +
  7.1416 +	The frame request will take effect on the next wl_surface.commit.
  7.1417 +	The notification will only be posted for one frame unless
  7.1418 +	requested again. For a wl_surface, the notifications are posted in
  7.1419 +	the order the frame requests were committed.
  7.1420 +
  7.1421 +	The server must send the notifications so that a client
  7.1422 +	will not send excessive updates, while still allowing
  7.1423 +	the highest possible update rate for clients that wait for the reply
  7.1424 +	before drawing again. The server should give some time for the client
  7.1425 +	to draw and commit after sending the frame callback events to let it
  7.1426 +	hit the next output refresh.
  7.1427 +
  7.1428 +	A server should avoid signaling the frame callbacks if the
  7.1429 +	surface is not visible in any way, e.g. the surface is off-screen,
  7.1430 +	or completely obscured by other opaque surfaces.
  7.1431 +
  7.1432 +	The object returned by this request will be destroyed by the
  7.1433 +	compositor after the callback is fired and as such the client must not
  7.1434 +	attempt to use it after that point.
  7.1435 +
  7.1436 +	The callback_data passed in the callback is the current time, in
  7.1437 +	milliseconds, with an undefined base.
  7.1438 +      </description>
  7.1439 +      <arg name="callback" type="new_id" interface="wl_callback" summary="callback object for the frame request"/>
  7.1440 +    </request>
  7.1441 +
  7.1442 +    <request name="set_opaque_region">
  7.1443 +      <description summary="set opaque region">
  7.1444 +	This request sets the region of the surface that contains
  7.1445 +	opaque content.
  7.1446 +
  7.1447 +	The opaque region is an optimization hint for the compositor
  7.1448 +	that lets it optimize the redrawing of content behind opaque
  7.1449 +	regions.  Setting an opaque region is not required for correct
  7.1450 +	behaviour, but marking transparent content as opaque will result
  7.1451 +	in repaint artifacts.
  7.1452 +
  7.1453 +	The opaque region is specified in surface-local coordinates.
  7.1454 +
  7.1455 +	The compositor ignores the parts of the opaque region that fall
  7.1456 +	outside of the surface.
  7.1457 +
  7.1458 +	Opaque region is double-buffered state, see wl_surface.commit.
  7.1459 +
  7.1460 +	wl_surface.set_opaque_region changes the pending opaque region.
  7.1461 +	wl_surface.commit copies the pending region to the current region.
  7.1462 +	Otherwise, the pending and current regions are never changed.
  7.1463 +
  7.1464 +	The initial value for an opaque region is empty. Setting the pending
  7.1465 +	opaque region has copy semantics, and the wl_region object can be
  7.1466 +	destroyed immediately. A NULL wl_region causes the pending opaque
  7.1467 +	region to be set to empty.
  7.1468 +      </description>
  7.1469 +      <arg name="region" type="object" interface="wl_region" allow-null="true"
  7.1470 +	   summary="opaque region of the surface"/>
  7.1471 +    </request>
  7.1472 +
  7.1473 +    <request name="set_input_region">
  7.1474 +      <description summary="set input region">
  7.1475 +	This request sets the region of the surface that can receive
  7.1476 +	pointer and touch events.
  7.1477 +
  7.1478 +	Input events happening outside of this region will try the next
  7.1479 +	surface in the server surface stack. The compositor ignores the
  7.1480 +	parts of the input region that fall outside of the surface.
  7.1481 +
  7.1482 +	The input region is specified in surface-local coordinates.
  7.1483 +
  7.1484 +	Input region is double-buffered state, see wl_surface.commit.
  7.1485 +
  7.1486 +	wl_surface.set_input_region changes the pending input region.
  7.1487 +	wl_surface.commit copies the pending region to the current region.
  7.1488 +	Otherwise the pending and current regions are never changed,
  7.1489 +	except cursor and icon surfaces are special cases, see
  7.1490 +	wl_pointer.set_cursor and wl_data_device.start_drag.
  7.1491 +
  7.1492 +	The initial value for an input region is infinite. That means the
  7.1493 +	whole surface will accept input. Setting the pending input region
  7.1494 +	has copy semantics, and the wl_region object can be destroyed
  7.1495 +	immediately. A NULL wl_region causes the input region to be set
  7.1496 +	to infinite.
  7.1497 +      </description>
  7.1498 +      <arg name="region" type="object" interface="wl_region" allow-null="true"
  7.1499 +	   summary="input region of the surface"/>
  7.1500 +    </request>
  7.1501 +
  7.1502 +    <request name="commit">
  7.1503 +      <description summary="commit pending surface state">
  7.1504 +	Surface state (input, opaque, and damage regions, attached buffers,
  7.1505 +	etc.) is double-buffered. Protocol requests modify the pending state,
  7.1506 +	as opposed to the current state in use by the compositor. A commit
  7.1507 +	request atomically applies all pending state, replacing the current
  7.1508 +	state. After commit, the new pending state is as documented for each
  7.1509 +	related request.
  7.1510 +
  7.1511 +	On commit, a pending wl_buffer is applied first, and all other state
  7.1512 +	second. This means that all coordinates in double-buffered state are
  7.1513 +	relative to the new wl_buffer coming into use, except for
  7.1514 +	wl_surface.attach itself. If there is no pending wl_buffer, the
  7.1515 +	coordinates are relative to the current surface contents.
  7.1516 +
  7.1517 +	All requests that need a commit to become effective are documented
  7.1518 +	to affect double-buffered state.
  7.1519 +
  7.1520 +	Other interfaces may add further double-buffered surface state.
  7.1521 +      </description>
  7.1522 +    </request>
  7.1523 +
  7.1524 +    <event name="enter">
  7.1525 +      <description summary="surface enters an output">
  7.1526 +	This is emitted whenever a surface's creation, movement, or resizing
  7.1527 +	results in some part of it being within the scanout region of an
  7.1528 +	output.
  7.1529 +
  7.1530 +	Note that a surface may be overlapping with zero or more outputs.
  7.1531 +      </description>
  7.1532 +      <arg name="output" type="object" interface="wl_output" summary="output entered by the surface"/>
  7.1533 +    </event>
  7.1534 +
  7.1535 +    <event name="leave">
  7.1536 +      <description summary="surface leaves an output">
  7.1537 +	This is emitted whenever a surface's creation, movement, or resizing
  7.1538 +	results in it no longer having any part of it within the scanout region
  7.1539 +	of an output.
  7.1540 +      </description>
  7.1541 +      <arg name="output" type="object" interface="wl_output" summary="output left by the surface"/>
  7.1542 +    </event>
  7.1543 +
  7.1544 +    <!-- Version 2 additions -->
  7.1545 +
  7.1546 +    <request name="set_buffer_transform" since="2">
  7.1547 +      <description summary="sets the buffer transformation">
  7.1548 +	This request sets an optional transformation on how the compositor
  7.1549 +	interprets the contents of the buffer attached to the surface. The
  7.1550 +	accepted values for the transform parameter are the values for
  7.1551 +	wl_output.transform.
  7.1552 +
  7.1553 +	Buffer transform is double-buffered state, see wl_surface.commit.
  7.1554 +
  7.1555 +	A newly created surface has its buffer transformation set to normal.
  7.1556 +
  7.1557 +	wl_surface.set_buffer_transform changes the pending buffer
  7.1558 +	transformation. wl_surface.commit copies the pending buffer
  7.1559 +	transformation to the current one. Otherwise, the pending and current
  7.1560 +	values are never changed.
  7.1561 +
  7.1562 +	The purpose of this request is to allow clients to render content
  7.1563 +	according to the output transform, thus permitting the compositor to
  7.1564 +	use certain optimizations even if the display is rotated. Using
  7.1565 +	hardware overlays and scanning out a client buffer for fullscreen
  7.1566 +	surfaces are examples of such optimizations. Those optimizations are
  7.1567 +	highly dependent on the compositor implementation, so the use of this
  7.1568 +	request should be considered on a case-by-case basis.
  7.1569 +
  7.1570 +	Note that if the transform value includes 90 or 270 degree rotation,
  7.1571 +	the width of the buffer will become the surface height and the height
  7.1572 +	of the buffer will become the surface width.
  7.1573 +
  7.1574 +	If transform is not one of the values from the
  7.1575 +	wl_output.transform enum the invalid_transform protocol error
  7.1576 +	is raised.
  7.1577 +      </description>
  7.1578 +      <arg name="transform" type="int" enum="wl_output.transform"
  7.1579 +	   summary="transform for interpreting buffer contents"/>
  7.1580 +    </request>
  7.1581 +
  7.1582 +    <!-- Version 3 additions -->
  7.1583 +
  7.1584 +    <request name="set_buffer_scale" since="3">
  7.1585 +      <description summary="sets the buffer scaling factor">
  7.1586 +	This request sets an optional scaling factor on how the compositor
  7.1587 +	interprets the contents of the buffer attached to the window.
  7.1588 +
  7.1589 +	Buffer scale is double-buffered state, see wl_surface.commit.
  7.1590 +
  7.1591 +	A newly created surface has its buffer scale set to 1.
  7.1592 +
  7.1593 +	wl_surface.set_buffer_scale changes the pending buffer scale.
  7.1594 +	wl_surface.commit copies the pending buffer scale to the current one.
  7.1595 +	Otherwise, the pending and current values are never changed.
  7.1596 +
  7.1597 +	The purpose of this request is to allow clients to supply higher
  7.1598 +	resolution buffer data for use on high resolution outputs. It is
  7.1599 +	intended that you pick the same buffer scale as the scale of the
  7.1600 +	output that the surface is displayed on. This means the compositor
  7.1601 +	can avoid scaling when rendering the surface on that output.
  7.1602 +
  7.1603 +	Note that if the scale is larger than 1, then you have to attach
  7.1604 +	a buffer that is larger (by a factor of scale in each dimension)
  7.1605 +	than the desired surface size.
  7.1606 +
  7.1607 +	If scale is not positive the invalid_scale protocol error is
  7.1608 +	raised.
  7.1609 +      </description>
  7.1610 +      <arg name="scale" type="int"
  7.1611 +	   summary="positive scale for interpreting buffer contents"/>
  7.1612 +    </request>
  7.1613 +
  7.1614 +    <!-- Version 4 additions -->
  7.1615 +    <request name="damage_buffer" since="4">
  7.1616 +      <description summary="mark part of the surface damaged using buffer coordinates">
  7.1617 +	This request is used to describe the regions where the pending
  7.1618 +	buffer is different from the current surface contents, and where
  7.1619 +	the surface therefore needs to be repainted. The compositor
  7.1620 +	ignores the parts of the damage that fall outside of the surface.
  7.1621 +
  7.1622 +	Damage is double-buffered state, see wl_surface.commit.
  7.1623 +
  7.1624 +	The damage rectangle is specified in buffer coordinates,
  7.1625 +	where x and y specify the upper left corner of the damage rectangle.
  7.1626 +
  7.1627 +	The initial value for pending damage is empty: no damage.
  7.1628 +	wl_surface.damage_buffer adds pending damage: the new pending
  7.1629 +	damage is the union of old pending damage and the given rectangle.
  7.1630 +
  7.1631 +	wl_surface.commit assigns pending damage as the current damage,
  7.1632 +	and clears pending damage. The server will clear the current
  7.1633 +	damage as it repaints the surface.
  7.1634 +
  7.1635 +	This request differs from wl_surface.damage in only one way - it
  7.1636 +	takes damage in buffer coordinates instead of surface-local
  7.1637 +	coordinates. While this generally is more intuitive than surface
  7.1638 +	coordinates, it is especially desirable when using wp_viewport
  7.1639 +	or when a drawing library (like EGL) is unaware of buffer scale
  7.1640 +	and buffer transform.
  7.1641 +
  7.1642 +	Note: Because buffer transformation changes and damage requests may
  7.1643 +	be interleaved in the protocol stream, it is impossible to determine
  7.1644 +	the actual mapping between surface and buffer damage until
  7.1645 +	wl_surface.commit time. Therefore, compositors wishing to take both
  7.1646 +	kinds of damage into account will have to accumulate damage from the
  7.1647 +	two requests separately and only transform from one to the other
  7.1648 +	after receiving the wl_surface.commit.
  7.1649 +      </description>
  7.1650 +      <arg name="x" type="int" summary="buffer-local x coordinate"/>
  7.1651 +      <arg name="y" type="int" summary="buffer-local y coordinate"/>
  7.1652 +      <arg name="width" type="int" summary="width of damage rectangle"/>
  7.1653 +      <arg name="height" type="int" summary="height of damage rectangle"/>
  7.1654 +    </request>
  7.1655 +   </interface>
  7.1656 +
  7.1657 +  <interface name="wl_seat" version="6">
  7.1658 +    <description summary="group of input devices">
  7.1659 +      A seat is a group of keyboards, pointer and touch devices. This
  7.1660 +      object is published as a global during start up, or when such a
  7.1661 +      device is hot plugged.  A seat typically has a pointer and
  7.1662 +      maintains a keyboard focus and a pointer focus.
  7.1663 +    </description>
  7.1664 +
  7.1665 +    <enum name="capability" bitfield="true">
  7.1666 +      <description summary="seat capability bitmask">
  7.1667 +	This is a bitmask of capabilities this seat has; if a member is
  7.1668 +	set, then it is present on the seat.
  7.1669 +      </description>
  7.1670 +      <entry name="pointer" value="1" summary="the seat has pointer devices"/>
  7.1671 +      <entry name="keyboard" value="2" summary="the seat has one or more keyboards"/>
  7.1672 +      <entry name="touch" value="4" summary="the seat has touch devices"/>
  7.1673 +    </enum>
  7.1674 +
  7.1675 +    <event name="capabilities">
  7.1676 +      <description summary="seat capabilities changed">
  7.1677 +	This is emitted whenever a seat gains or loses the pointer,
  7.1678 +	keyboard or touch capabilities.  The argument is a capability
  7.1679 +	enum containing the complete set of capabilities this seat has.
  7.1680 +
  7.1681 +	When the pointer capability is added, a client may create a
  7.1682 +	wl_pointer object using the wl_seat.get_pointer request. This object
  7.1683 +	will receive pointer events until the capability is removed in the
  7.1684 +	future.
  7.1685 +
  7.1686 +	When the pointer capability is removed, a client should destroy the
  7.1687 +	wl_pointer objects associated with the seat where the capability was
  7.1688 +	removed, using the wl_pointer.release request. No further pointer
  7.1689 +	events will be received on these objects.
  7.1690 +
  7.1691 +	In some compositors, if a seat regains the pointer capability and a
  7.1692 +	client has a previously obtained wl_pointer object of version 4 or
  7.1693 +	less, that object may start sending pointer events again. This
  7.1694 +	behavior is considered a misinterpretation of the intended behavior
  7.1695 +	and must not be relied upon by the client. wl_pointer objects of
  7.1696 +	version 5 or later must not send events if created before the most
  7.1697 +	recent event notifying the client of an added pointer capability.
  7.1698 +
  7.1699 +	The above behavior also applies to wl_keyboard and wl_touch with the
  7.1700 +	keyboard and touch capabilities, respectively.
  7.1701 +      </description>
  7.1702 +      <arg name="capabilities" type="uint" enum="capability" summary="capabilities of the seat"/>
  7.1703 +    </event>
  7.1704 +
  7.1705 +    <request name="get_pointer">
  7.1706 +      <description summary="return pointer object">
  7.1707 +	The ID provided will be initialized to the wl_pointer interface
  7.1708 +	for this seat.
  7.1709 +
  7.1710 +	This request only takes effect if the seat has the pointer
  7.1711 +	capability, or has had the pointer capability in the past.
  7.1712 +	It is a protocol violation to issue this request on a seat that has
  7.1713 +	never had the pointer capability.
  7.1714 +      </description>
  7.1715 +      <arg name="id" type="new_id" interface="wl_pointer" summary="seat pointer"/>
  7.1716 +    </request>
  7.1717 +
  7.1718 +    <request name="get_keyboard">
  7.1719 +      <description summary="return keyboard object">
  7.1720 +	The ID provided will be initialized to the wl_keyboard interface
  7.1721 +	for this seat.
  7.1722 +
  7.1723 +	This request only takes effect if the seat has the keyboard
  7.1724 +	capability, or has had the keyboard capability in the past.
  7.1725 +	It is a protocol violation to issue this request on a seat that has
  7.1726 +	never had the keyboard capability.
  7.1727 +      </description>
  7.1728 +      <arg name="id" type="new_id" interface="wl_keyboard" summary="seat keyboard"/>
  7.1729 +    </request>
  7.1730 +
  7.1731 +    <request name="get_touch">
  7.1732 +      <description summary="return touch object">
  7.1733 +	The ID provided will be initialized to the wl_touch interface
  7.1734 +	for this seat.
  7.1735 +
  7.1736 +	This request only takes effect if the seat has the touch
  7.1737 +	capability, or has had the touch capability in the past.
  7.1738 +	It is a protocol violation to issue this request on a seat that has
  7.1739 +	never had the touch capability.
  7.1740 +      </description>
  7.1741 +      <arg name="id" type="new_id" interface="wl_touch" summary="seat touch interface"/>
  7.1742 +    </request>
  7.1743 +
  7.1744 +    <!-- Version 2 additions -->
  7.1745 +
  7.1746 +    <event name="name" since="2">
  7.1747 +      <description summary="unique identifier for this seat">
  7.1748 +	In a multiseat configuration this can be used by the client to help
  7.1749 +	identify which physical devices the seat represents. Based on
  7.1750 +	the seat configuration used by the compositor.
  7.1751 +      </description>
  7.1752 +      <arg name="name" type="string" summary="seat identifier"/>
  7.1753 +    </event>
  7.1754 +
  7.1755 +    <!-- Version 5 additions -->
  7.1756 +
  7.1757 +    <request name="release" type="destructor" since="5">
  7.1758 +      <description summary="release the seat object">
  7.1759 +	Using this request a client can tell the server that it is not going to
  7.1760 +	use the seat object anymore.
  7.1761 +      </description>
  7.1762 +    </request>
  7.1763 +
  7.1764 +  </interface>
  7.1765 +
  7.1766 +  <interface name="wl_pointer" version="6">
  7.1767 +    <description summary="pointer input device">
  7.1768 +      The wl_pointer interface represents one or more input devices,
  7.1769 +      such as mice, which control the pointer location and pointer_focus
  7.1770 +      of a seat.
  7.1771 +
  7.1772 +      The wl_pointer interface generates motion, enter and leave
  7.1773 +      events for the surfaces that the pointer is located over,
  7.1774 +      and button and axis events for button presses, button releases
  7.1775 +      and scrolling.
  7.1776 +    </description>
  7.1777 +
  7.1778 +    <enum name="error">
  7.1779 +      <entry name="role" value="0" summary="given wl_surface has another role"/>
  7.1780 +    </enum>
  7.1781 +
  7.1782 +    <request name="set_cursor">
  7.1783 +      <description summary="set the pointer surface">
  7.1784 +	Set the pointer surface, i.e., the surface that contains the
  7.1785 +	pointer image (cursor). This request gives the surface the role
  7.1786 +	of a cursor. If the surface already has another role, it raises
  7.1787 +	a protocol error.
  7.1788 +
  7.1789 +	The cursor actually changes only if the pointer
  7.1790 +	focus for this device is one of the requesting client's surfaces
  7.1791 +	or the surface parameter is the current pointer surface. If
  7.1792 +	there was a previous surface set with this request it is
  7.1793 +	replaced. If surface is NULL, the pointer image is hidden.
  7.1794 +
  7.1795 +	The parameters hotspot_x and hotspot_y define the position of
  7.1796 +	the pointer surface relative to the pointer location. Its
  7.1797 +	top-left corner is always at (x, y) - (hotspot_x, hotspot_y),
  7.1798 +	where (x, y) are the coordinates of the pointer location, in
  7.1799 +	surface-local coordinates.
  7.1800 +
  7.1801 +	On surface.attach requests to the pointer surface, hotspot_x
  7.1802 +	and hotspot_y are decremented by the x and y parameters
  7.1803 +	passed to the request. Attach must be confirmed by
  7.1804 +	wl_surface.commit as usual.
  7.1805 +
  7.1806 +	The hotspot can also be updated by passing the currently set
  7.1807 +	pointer surface to this request with new values for hotspot_x
  7.1808 +	and hotspot_y.
  7.1809 +
  7.1810 +	The current and pending input regions of the wl_surface are
  7.1811 +	cleared, and wl_surface.set_input_region is ignored until the
  7.1812 +	wl_surface is no longer used as the cursor. When the use as a
  7.1813 +	cursor ends, the current and pending input regions become
  7.1814 +	undefined, and the wl_surface is unmapped.
  7.1815 +      </description>
  7.1816 +      <arg name="serial" type="uint" summary="serial number of the enter event"/>
  7.1817 +      <arg name="surface" type="object" interface="wl_surface" allow-null="true"
  7.1818 +	   summary="pointer surface"/>
  7.1819 +      <arg name="hotspot_x" type="int" summary="surface-local x coordinate"/>
  7.1820 +      <arg name="hotspot_y" type="int" summary="surface-local y coordinate"/>
  7.1821 +    </request>
  7.1822 +
  7.1823 +    <event name="enter">
  7.1824 +      <description summary="enter event">
  7.1825 +	Notification that this seat's pointer is focused on a certain
  7.1826 +	surface.
  7.1827 +
  7.1828 +	When a seat's focus enters a surface, the pointer image
  7.1829 +	is undefined and a client should respond to this event by setting
  7.1830 +	an appropriate pointer image with the set_cursor request.
  7.1831 +      </description>
  7.1832 +      <arg name="serial" type="uint" summary="serial number of the enter event"/>
  7.1833 +      <arg name="surface" type="object" interface="wl_surface" summary="surface entered by the pointer"/>
  7.1834 +      <arg name="surface_x" type="fixed" summary="surface-local x coordinate"/>
  7.1835 +      <arg name="surface_y" type="fixed" summary="surface-local y coordinate"/>
  7.1836 +    </event>
  7.1837 +
  7.1838 +    <event name="leave">
  7.1839 +      <description summary="leave event">
  7.1840 +	Notification that this seat's pointer is no longer focused on
  7.1841 +	a certain surface.
  7.1842 +
  7.1843 +	The leave notification is sent before the enter notification
  7.1844 +	for the new focus.
  7.1845 +      </description>
  7.1846 +      <arg name="serial" type="uint" summary="serial number of the leave event"/>
  7.1847 +      <arg name="surface" type="object" interface="wl_surface" summary="surface left by the pointer"/>
  7.1848 +    </event>
  7.1849 +
  7.1850 +    <event name="motion">
  7.1851 +      <description summary="pointer motion event">
  7.1852 +	Notification of pointer location change. The arguments
  7.1853 +	surface_x and surface_y are the location relative to the
  7.1854 +	focused surface.
  7.1855 +      </description>
  7.1856 +      <arg name="time" type="uint" summary="timestamp with millisecond granularity"/>
  7.1857 +      <arg name="surface_x" type="fixed" summary="surface-local x coordinate"/>
  7.1858 +      <arg name="surface_y" type="fixed" summary="surface-local y coordinate"/>
  7.1859 +    </event>
  7.1860 +
  7.1861 +    <enum name="button_state">
  7.1862 +      <description summary="physical button state">
  7.1863 +	Describes the physical state of a button that produced the button
  7.1864 +	event.
  7.1865 +      </description>
  7.1866 +      <entry name="released" value="0" summary="the button is not pressed"/>
  7.1867 +      <entry name="pressed" value="1" summary="the button is pressed"/>
  7.1868 +    </enum>
  7.1869 +
  7.1870 +    <event name="button">
  7.1871 +      <description summary="pointer button event">
  7.1872 +	Mouse button click and release notifications.
  7.1873 +
  7.1874 +	The location of the click is given by the last motion or
  7.1875 +	enter event.
  7.1876 +	The time argument is a timestamp with millisecond
  7.1877 +	granularity, with an undefined base.
  7.1878 +
  7.1879 +	The button is a button code as defined in the Linux kernel's
  7.1880 +	linux/input-event-codes.h header file, e.g. BTN_LEFT.
  7.1881 +
  7.1882 +	Any 16-bit button code value is reserved for future additions to the
  7.1883 +	kernel's event code list. All other button codes above 0xFFFF are
  7.1884 +	currently undefined but may be used in future versions of this
  7.1885 +	protocol.
  7.1886 +      </description>
  7.1887 +      <arg name="serial" type="uint" summary="serial number of the button event"/>
  7.1888 +      <arg name="time" type="uint" summary="timestamp with millisecond granularity"/>
  7.1889 +      <arg name="button" type="uint" summary="button that produced the event"/>
  7.1890 +      <arg name="state" type="uint" enum="button_state" summary="physical state of the button"/>
  7.1891 +    </event>
  7.1892 +
  7.1893 +    <enum name="axis">
  7.1894 +      <description summary="axis types">
  7.1895 +	Describes the axis types of scroll events.
  7.1896 +      </description>
  7.1897 +      <entry name="vertical_scroll" value="0" summary="vertical axis"/>
  7.1898 +      <entry name="horizontal_scroll" value="1" summary="horizontal axis"/>
  7.1899 +    </enum>
  7.1900 +
  7.1901 +    <event name="axis">
  7.1902 +      <description summary="axis event">
  7.1903 +	Scroll and other axis notifications.
  7.1904 +
  7.1905 +	For scroll events (vertical and horizontal scroll axes), the
  7.1906 +	value parameter is the length of a vector along the specified
  7.1907 +	axis in a coordinate space identical to those of motion events,
  7.1908 +	representing a relative movement along the specified axis.
  7.1909 +
  7.1910 +	For devices that support movements non-parallel to axes multiple
  7.1911 +	axis events will be emitted.
  7.1912 +
  7.1913 +	When applicable, for example for touch pads, the server can
  7.1914 +	choose to emit scroll events where the motion vector is
  7.1915 +	equivalent to a motion event vector.
  7.1916 +
  7.1917 +	When applicable, a client can transform its content relative to the
  7.1918 +	scroll distance.
  7.1919 +      </description>
  7.1920 +      <arg name="time" type="uint" summary="timestamp with millisecond granularity"/>
  7.1921 +      <arg name="axis" type="uint" enum="axis" summary="axis type"/>
  7.1922 +      <arg name="value" type="fixed" summary="length of vector in surface-local coordinate space"/>
  7.1923 +    </event>
  7.1924 +
  7.1925 +    <!-- Version 3 additions -->
  7.1926 +
  7.1927 +    <request name="release" type="destructor" since="3">
  7.1928 +      <description summary="release the pointer object">
  7.1929 +	Using this request a client can tell the server that it is not going to
  7.1930 +	use the pointer object anymore.
  7.1931 +
  7.1932 +	This request destroys the pointer proxy object, so clients must not call
  7.1933 +	wl_pointer_destroy() after using this request.
  7.1934 +      </description>
  7.1935 +    </request>
  7.1936 +
  7.1937 +    <!-- Version 5 additions -->
  7.1938 +
  7.1939 +    <event name="frame" since="5">
  7.1940 +      <description summary="end of a pointer event sequence">
  7.1941 +	Indicates the end of a set of events that logically belong together.
  7.1942 +	A client is expected to accumulate the data in all events within the
  7.1943 +	frame before proceeding.
  7.1944 +
  7.1945 +	All wl_pointer events before a wl_pointer.frame event belong
  7.1946 +	logically together. For example, in a diagonal scroll motion the
  7.1947 +	compositor will send an optional wl_pointer.axis_source event, two
  7.1948 +	wl_pointer.axis events (horizontal and vertical) and finally a
  7.1949 +	wl_pointer.frame event. The client may use this information to
  7.1950 +	calculate a diagonal vector for scrolling.
  7.1951 +
  7.1952 +	When multiple wl_pointer.axis events occur within the same frame,
  7.1953 +	the motion vector is the combined motion of all events.
  7.1954 +	When a wl_pointer.axis and a wl_pointer.axis_stop event occur within
  7.1955 +	the same frame, this indicates that axis movement in one axis has
  7.1956 +	stopped but continues in the other axis.
  7.1957 +	When multiple wl_pointer.axis_stop events occur within the same
  7.1958 +	frame, this indicates that these axes stopped in the same instance.
  7.1959 +
  7.1960 +	A wl_pointer.frame event is sent for every logical event group,
  7.1961 +	even if the group only contains a single wl_pointer event.
  7.1962 +	Specifically, a client may get a sequence: motion, frame, button,
  7.1963 +	frame, axis, frame, axis_stop, frame.
  7.1964 +
  7.1965 +	The wl_pointer.enter and wl_pointer.leave events are logical events
  7.1966 +	generated by the compositor and not the hardware. These events are
  7.1967 +	also grouped by a wl_pointer.frame. When a pointer moves from one
  7.1968 +	surface to another, a compositor should group the
  7.1969 +	wl_pointer.leave event within the same wl_pointer.frame.
  7.1970 +	However, a client must not rely on wl_pointer.leave and
  7.1971 +	wl_pointer.enter being in the same wl_pointer.frame.
  7.1972 +	Compositor-specific policies may require the wl_pointer.leave and
  7.1973 +	wl_pointer.enter event being split across multiple wl_pointer.frame
  7.1974 +	groups.
  7.1975 +      </description>
  7.1976 +    </event>
  7.1977 +
  7.1978 +    <enum name="axis_source">
  7.1979 +      <description summary="axis source types">
  7.1980 +	Describes the source types for axis events. This indicates to the
  7.1981 +	client how an axis event was physically generated; a client may
  7.1982 +	adjust the user interface accordingly. For example, scroll events
  7.1983 +	from a "finger" source may be in a smooth coordinate space with
  7.1984 +	kinetic scrolling whereas a "wheel" source may be in discrete steps
  7.1985 +	of a number of lines.
  7.1986 +
  7.1987 +	The "continuous" axis source is a device generating events in a
  7.1988 +	continuous coordinate space, but using something other than a
  7.1989 +	finger. One example for this source is button-based scrolling where
  7.1990 +	the vertical motion of a device is converted to scroll events while
  7.1991 +	a button is held down.
  7.1992 +
  7.1993 +	The "wheel tilt" axis source indicates that the actual device is a
  7.1994 +	wheel but the scroll event is not caused by a rotation but a
  7.1995 +	(usually sideways) tilt of the wheel.
  7.1996 +      </description>
  7.1997 +      <entry name="wheel" value="0" summary="a physical wheel rotation" />
  7.1998 +      <entry name="finger" value="1" summary="finger on a touch surface" />
  7.1999 +      <entry name="continuous" value="2" summary="continuous coordinate space"/>
  7.2000 +      <entry name="wheel_tilt" value="3" summary="a physical wheel tilt" since="6"/>
  7.2001 +    </enum>
  7.2002 +
  7.2003 +    <event name="axis_source" since="5">
  7.2004 +      <description summary="axis source event">
  7.2005 +	Source information for scroll and other axes.
  7.2006 +
  7.2007 +	This event does not occur on its own. It is sent before a
  7.2008 +	wl_pointer.frame event and carries the source information for
  7.2009 +	all events within that frame.
  7.2010 +
  7.2011 +	The source specifies how this event was generated. If the source is
  7.2012 +	wl_pointer.axis_source.finger, a wl_pointer.axis_stop event will be
  7.2013 +	sent when the user lifts the finger off the device.
  7.2014 +
  7.2015 +	If the source is wl_pointer.axis_source.wheel,
  7.2016 +	wl_pointer.axis_source.wheel_tilt or
  7.2017 +	wl_pointer.axis_source.continuous, a wl_pointer.axis_stop event may
  7.2018 +	or may not be sent. Whether a compositor sends an axis_stop event
  7.2019 +	for these sources is hardware-specific and implementation-dependent;
  7.2020 +	clients must not rely on receiving an axis_stop event for these
  7.2021 +	scroll sources and should treat scroll sequences from these scroll
  7.2022 +	sources as unterminated by default.
  7.2023 +
  7.2024 +	This event is optional. If the source is unknown for a particular
  7.2025 +	axis event sequence, no event is sent.
  7.2026 +	Only one wl_pointer.axis_source event is permitted per frame.
  7.2027 +
  7.2028 +	The order of wl_pointer.axis_discrete and wl_pointer.axis_source is
  7.2029 +	not guaranteed.
  7.2030 +      </description>
  7.2031 +      <arg name="axis_source" type="uint" enum="axis_source" summary="source of the axis event"/>
  7.2032 +    </event>
  7.2033 +
  7.2034 +    <event name="axis_stop" since="5">
  7.2035 +      <description summary="axis stop event">
  7.2036 +	Stop notification for scroll and other axes.
  7.2037 +
  7.2038 +	For some wl_pointer.axis_source types, a wl_pointer.axis_stop event
  7.2039 +	is sent to notify a client that the axis sequence has terminated.
  7.2040 +	This enables the client to implement kinetic scrolling.
  7.2041 +	See the wl_pointer.axis_source documentation for information on when
  7.2042 +	this event may be generated.
  7.2043 +
  7.2044 +	Any wl_pointer.axis events with the same axis_source after this
  7.2045 +	event should be considered as the start of a new axis motion.
  7.2046 +
  7.2047 +	The timestamp is to be interpreted identical to the timestamp in the
  7.2048 +	wl_pointer.axis event. The timestamp value may be the same as a
  7.2049 +	preceding wl_pointer.axis event.
  7.2050 +      </description>
  7.2051 +      <arg name="time" type="uint" summary="timestamp with millisecond granularity"/>
  7.2052 +      <arg name="axis" type="uint" enum="axis" summary="the axis stopped with this event"/>
  7.2053 +    </event>
  7.2054 +
  7.2055 +    <event name="axis_discrete" since="5">
  7.2056 +      <description summary="axis click event">
  7.2057 +	Discrete step information for scroll and other axes.
  7.2058 +
  7.2059 +	This event carries the axis value of the wl_pointer.axis event in
  7.2060 +	discrete steps (e.g. mouse wheel clicks).
  7.2061 +
  7.2062 +	This event does not occur on its own, it is coupled with a
  7.2063 +	wl_pointer.axis event that represents this axis value on a
  7.2064 +	continuous scale. The protocol guarantees that each axis_discrete
  7.2065 +	event is always followed by exactly one axis event with the same
  7.2066 +	axis number within the same wl_pointer.frame. Note that the protocol
  7.2067 +	allows for other events to occur between the axis_discrete and
  7.2068 +	its coupled axis event, including other axis_discrete or axis
  7.2069 +	events.
  7.2070 +
  7.2071 +	This event is optional; continuous scrolling devices
  7.2072 +	like two-finger scrolling on touchpads do not have discrete
  7.2073 +	steps and do not generate this event.
  7.2074 +
  7.2075 +	The discrete value carries the directional information. e.g. a value
  7.2076 +	of -2 is two steps towards the negative direction of this axis.
  7.2077 +
  7.2078 +	The axis number is identical to the axis number in the associated
  7.2079 +	axis event.
  7.2080 +
  7.2081 +	The order of wl_pointer.axis_discrete and wl_pointer.axis_source is
  7.2082 +	not guaranteed.
  7.2083 +      </description>
  7.2084 +      <arg name="axis" type="uint" enum="axis" summary="axis type"/>
  7.2085 +      <arg name="discrete" type="int" summary="number of steps"/>
  7.2086 +    </event>
  7.2087 +  </interface>
  7.2088 +
  7.2089 +  <interface name="wl_keyboard" version="6">
  7.2090 +    <description summary="keyboard input device">
  7.2091 +      The wl_keyboard interface represents one or more keyboards
  7.2092 +      associated with a seat.
  7.2093 +    </description>
  7.2094 +
  7.2095 +    <enum name="keymap_format">
  7.2096 +      <description summary="keyboard mapping format">
  7.2097 +	This specifies the format of the keymap provided to the
  7.2098 +	client with the wl_keyboard.keymap event.
  7.2099 +      </description>
  7.2100 +      <entry name="no_keymap" value="0"
  7.2101 +	     summary="no keymap; client must understand how to interpret the raw keycode"/>
  7.2102 +      <entry name="xkb_v1" value="1"
  7.2103 +	     summary="libxkbcommon compatible; to determine the xkb keycode, clients must add 8 to the key event keycode"/>
  7.2104 +    </enum>
  7.2105 +
  7.2106 +    <event name="keymap">
  7.2107 +      <description summary="keyboard mapping">
  7.2108 +	This event provides a file descriptor to the client which can be
  7.2109 +	memory-mapped to provide a keyboard mapping description.
  7.2110 +      </description>
  7.2111 +      <arg name="format" type="uint" enum="keymap_format" summary="keymap format"/>
  7.2112 +      <arg name="fd" type="fd" summary="keymap file descriptor"/>
  7.2113 +      <arg name="size" type="uint" summary="keymap size, in bytes"/>
  7.2114 +    </event>
  7.2115 +
  7.2116 +    <event name="enter">
  7.2117 +      <description summary="enter event">
  7.2118 +	Notification that this seat's keyboard focus is on a certain
  7.2119 +	surface.
  7.2120 +      </description>
  7.2121 +      <arg name="serial" type="uint" summary="serial number of the enter event"/>
  7.2122 +      <arg name="surface" type="object" interface="wl_surface" summary="surface gaining keyboard focus"/>
  7.2123 +      <arg name="keys" type="array" summary="the currently pressed keys"/>
  7.2124 +    </event>
  7.2125 +
  7.2126 +    <event name="leave">
  7.2127 +      <description summary="leave event">
  7.2128 +	Notification that this seat's keyboard focus is no longer on
  7.2129 +	a certain surface.
  7.2130 +
  7.2131 +	The leave notification is sent before the enter notification
  7.2132 +	for the new focus.
  7.2133 +      </description>
  7.2134 +      <arg name="serial" type="uint" summary="serial number of the leave event"/>
  7.2135 +      <arg name="surface" type="object" interface="wl_surface" summary="surface that lost keyboard focus"/>
  7.2136 +    </event>
  7.2137 +
  7.2138 +    <enum name="key_state">
  7.2139 +      <description summary="physical key state">
  7.2140 +	Describes the physical state of a key that produced the key event.
  7.2141 +      </description>
  7.2142 +      <entry name="released" value="0" summary="key is not pressed"/>
  7.2143 +      <entry name="pressed" value="1" summary="key is pressed"/>
  7.2144 +    </enum>
  7.2145 +
  7.2146 +    <event name="key">
  7.2147 +      <description summary="key event">
  7.2148 +	A key was pressed or released.
  7.2149 +	The time argument is a timestamp with millisecond
  7.2150 +	granularity, with an undefined base.
  7.2151 +      </description>
  7.2152 +      <arg name="serial" type="uint" summary="serial number of the key event"/>
  7.2153 +      <arg name="time" type="uint" summary="timestamp with millisecond granularity"/>
  7.2154 +      <arg name="key" type="uint" summary="key that produced the event"/>
  7.2155 +      <arg name="state" type="uint" enum="key_state" summary="physical state of the key"/>
  7.2156 +    </event>
  7.2157 +
  7.2158 +    <event name="modifiers">
  7.2159 +      <description summary="modifier and group state">
  7.2160 +	Notifies clients that the modifier and/or group state has
  7.2161 +	changed, and it should update its local state.
  7.2162 +      </description>
  7.2163 +      <arg name="serial" type="uint" summary="serial number of the modifiers event"/>
  7.2164 +      <arg name="mods_depressed" type="uint" summary="depressed modifiers"/>
  7.2165 +      <arg name="mods_latched" type="uint" summary="latched modifiers"/>
  7.2166 +      <arg name="mods_locked" type="uint" summary="locked modifiers"/>
  7.2167 +      <arg name="group" type="uint" summary="keyboard layout"/>
  7.2168 +    </event>
  7.2169 +
  7.2170 +    <!-- Version 3 additions -->
  7.2171 +
  7.2172 +    <request name="release" type="destructor" since="3">
  7.2173 +      <description summary="release the keyboard object"/>
  7.2174 +    </request>
  7.2175 +
  7.2176 +    <!-- Version 4 additions -->
  7.2177 +
  7.2178 +    <event name="repeat_info" since="4">
  7.2179 +      <description summary="repeat rate and delay">
  7.2180 +	Informs the client about the keyboard's repeat rate and delay.
  7.2181 +
  7.2182 +	This event is sent as soon as the wl_keyboard object has been created,
  7.2183 +	and is guaranteed to be received by the client before any key press
  7.2184 +	event.
  7.2185 +
  7.2186 +	Negative values for either rate or delay are illegal. A rate of zero
  7.2187 +	will disable any repeating (regardless of the value of delay).
  7.2188 +
  7.2189 +	This event can be sent later on as well with a new value if necessary,
  7.2190 +	so clients should continue listening for the event past the creation
  7.2191 +	of wl_keyboard.
  7.2192 +      </description>
  7.2193 +      <arg name="rate" type="int"
  7.2194 +	   summary="the rate of repeating keys in characters per second"/>
  7.2195 +      <arg name="delay" type="int"
  7.2196 +	   summary="delay in milliseconds since key down until repeating starts"/>
  7.2197 +    </event>
  7.2198 +  </interface>
  7.2199 +
  7.2200 +  <interface name="wl_touch" version="6">
  7.2201 +    <description summary="touchscreen input device">
  7.2202 +      The wl_touch interface represents a touchscreen
  7.2203 +      associated with a seat.
  7.2204 +
  7.2205 +      Touch interactions can consist of one or more contacts.
  7.2206 +      For each contact, a series of events is generated, starting
  7.2207 +      with a down event, followed by zero or more motion events,
  7.2208 +      and ending with an up event. Events relating to the same
  7.2209 +      contact point can be identified by the ID of the sequence.
  7.2210 +    </description>
  7.2211 +
  7.2212 +    <event name="down">
  7.2213 +      <description summary="touch down event and beginning of a touch sequence">
  7.2214 +	A new touch point has appeared on the surface. This touch point is
  7.2215 +	assigned a unique ID. Future events from this touch point reference
  7.2216 +	this ID. The ID ceases to be valid after a touch up event and may be
  7.2217 +	reused in the future.
  7.2218 +      </description>
  7.2219 +      <arg name="serial" type="uint" summary="serial number of the touch down event"/>
  7.2220 +      <arg name="time" type="uint" summary="timestamp with millisecond granularity"/>
  7.2221 +      <arg name="surface" type="object" interface="wl_surface" summary="surface touched"/>
  7.2222 +      <arg name="id" type="int" summary="the unique ID of this touch point"/>
  7.2223 +      <arg name="x" type="fixed" summary="surface-local x coordinate"/>
  7.2224 +      <arg name="y" type="fixed" summary="surface-local y coordinate"/>
  7.2225 +    </event>
  7.2226 +
  7.2227 +    <event name="up">
  7.2228 +      <description summary="end of a touch event sequence">
  7.2229 +	The touch point has disappeared. No further events will be sent for
  7.2230 +	this touch point and the touch point's ID is released and may be
  7.2231 +	reused in a future touch down event.
  7.2232 +      </description>
  7.2233 +      <arg name="serial" type="uint" summary="serial number of the touch up event"/>
  7.2234 +      <arg name="time" type="uint" summary="timestamp with millisecond granularity"/>
  7.2235 +      <arg name="id" type="int" summary="the unique ID of this touch point"/>
  7.2236 +    </event>
  7.2237 +
  7.2238 +    <event name="motion">
  7.2239 +      <description summary="update of touch point coordinates">
  7.2240 +	A touch point has changed coordinates.
  7.2241 +      </description>
  7.2242 +      <arg name="time" type="uint" summary="timestamp with millisecond granularity"/>
  7.2243 +      <arg name="id" type="int" summary="the unique ID of this touch point"/>
  7.2244 +      <arg name="x" type="fixed" summary="surface-local x coordinate"/>
  7.2245 +      <arg name="y" type="fixed" summary="surface-local y coordinate"/>
  7.2246 +    </event>
  7.2247 +
  7.2248 +    <event name="frame">
  7.2249 +      <description summary="end of touch frame event">
  7.2250 +	Indicates the end of a set of events that logically belong together.
  7.2251 +	A client is expected to accumulate the data in all events within the
  7.2252 +	frame before proceeding.
  7.2253 +
  7.2254 +	A wl_touch.frame terminates at least one event but otherwise no
  7.2255 +	guarantee is provided about the set of events within a frame. A client
  7.2256 +	must assume that any state not updated in a frame is unchanged from the
  7.2257 +	previously known state.
  7.2258 +      </description>
  7.2259 +    </event>
  7.2260 +
  7.2261 +    <event name="cancel">
  7.2262 +      <description summary="touch session cancelled">
  7.2263 +	Sent if the compositor decides the touch stream is a global
  7.2264 +	gesture. No further events are sent to the clients from that
  7.2265 +	particular gesture. Touch cancellation applies to all touch points
  7.2266 +	currently active on this client's surface. The client is
  7.2267 +	responsible for finalizing the touch points, future touch points on
  7.2268 +	this surface may reuse the touch point ID.
  7.2269 +      </description>
  7.2270 +    </event>
  7.2271 +
  7.2272 +    <!-- Version 3 additions -->
  7.2273 +
  7.2274 +    <request name="release" type="destructor" since="3">
  7.2275 +      <description summary="release the touch object"/>
  7.2276 +    </request>
  7.2277 +
  7.2278 +    <!-- Version 6 additions -->
  7.2279 +
  7.2280 +    <event name="shape" since="6">
  7.2281 +      <description summary="update shape of touch point">
  7.2282 +	Sent when a touchpoint has changed its shape.
  7.2283 +
  7.2284 +	This event does not occur on its own. It is sent before a
  7.2285 +	wl_touch.frame event and carries the new shape information for
  7.2286 +	any previously reported, or new touch points of that frame.
  7.2287 +
  7.2288 +	Other events describing the touch point such as wl_touch.down,
  7.2289 +	wl_touch.motion or wl_touch.orientation may be sent within the
  7.2290 +	same wl_touch.frame. A client should treat these events as a single
  7.2291 +	logical touch point update. The order of wl_touch.shape,
  7.2292 +	wl_touch.orientation and wl_touch.motion is not guaranteed.
  7.2293 +	A wl_touch.down event is guaranteed to occur before the first
  7.2294 +	wl_touch.shape event for this touch ID but both events may occur within
  7.2295 +	the same wl_touch.frame.
  7.2296 +
  7.2297 +	A touchpoint shape is approximated by an ellipse through the major and
  7.2298 +	minor axis length. The major axis length describes the longer diameter
  7.2299 +	of the ellipse, while the minor axis length describes the shorter
  7.2300 +	diameter. Major and minor are orthogonal and both are specified in
  7.2301 +	surface-local coordinates. The center of the ellipse is always at the
  7.2302 +	touchpoint location as reported by wl_touch.down or wl_touch.move.
  7.2303 +
  7.2304 +	This event is only sent by the compositor if the touch device supports
  7.2305 +	shape reports. The client has to make reasonable assumptions about the
  7.2306 +	shape if it did not receive this event.
  7.2307 +      </description>
  7.2308 +      <arg name="id" type="int" summary="the unique ID of this touch point"/>
  7.2309 +      <arg name="major" type="fixed" summary="length of the major axis in surface-local coordinates"/>
  7.2310 +      <arg name="minor" type="fixed" summary="length of the minor axis in surface-local coordinates"/>
  7.2311 +    </event>
  7.2312 +
  7.2313 +    <event name="orientation" since="6">
  7.2314 +      <description summary="update orientation of touch point">
  7.2315 +	Sent when a touchpoint has changed its orientation.
  7.2316 +
  7.2317 +	This event does not occur on its own. It is sent before a
  7.2318 +	wl_touch.frame event and carries the new shape information for
  7.2319 +	any previously reported, or new touch points of that frame.
  7.2320 +
  7.2321 +	Other events describing the touch point such as wl_touch.down,
  7.2322 +	wl_touch.motion or wl_touch.shape may be sent within the
  7.2323 +	same wl_touch.frame. A client should treat these events as a single
  7.2324 +	logical touch point update. The order of wl_touch.shape,
  7.2325 +	wl_touch.orientation and wl_touch.motion is not guaranteed.
  7.2326 +	A wl_touch.down event is guaranteed to occur before the first
  7.2327 +	wl_touch.orientation event for this touch ID but both events may occur
  7.2328 +	within the same wl_touch.frame.
  7.2329 +
  7.2330 +	The orientation describes the clockwise angle of a touchpoint's major
  7.2331 +	axis to the positive surface y-axis and is normalized to the -180 to
  7.2332 +	+180 degree range. The granularity of orientation depends on the touch
  7.2333 +	device, some devices only support binary rotation values between 0 and
  7.2334 +	90 degrees.
  7.2335 +
  7.2336 +	This event is only sent by the compositor if the touch device supports
  7.2337 +	orientation reports.
  7.2338 +      </description>
  7.2339 +      <arg name="id" type="int" summary="the unique ID of this touch point"/>
  7.2340 +      <arg name="orientation" type="fixed" summary="angle between major axis and positive surface y-axis in degrees"/>
  7.2341 +    </event>
  7.2342 +  </interface>
  7.2343 +
  7.2344 +  <interface name="wl_output" version="3">
  7.2345 +    <description summary="compositor output region">
  7.2346 +      An output describes part of the compositor geometry.  The
  7.2347 +      compositor works in the 'compositor coordinate system' and an
  7.2348 +      output corresponds to a rectangular area in that space that is
  7.2349 +      actually visible.  This typically corresponds to a monitor that
  7.2350 +      displays part of the compositor space.  This object is published
  7.2351 +      as global during start up, or when a monitor is hotplugged.
  7.2352 +    </description>
  7.2353 +
  7.2354 +    <enum name="subpixel">
  7.2355 +      <description summary="subpixel geometry information">
  7.2356 +	This enumeration describes how the physical
  7.2357 +	pixels on an output are laid out.
  7.2358 +      </description>
  7.2359 +      <entry name="unknown" value="0" summary="unknown geometry"/>
  7.2360 +      <entry name="none" value="1" summary="no geometry"/>
  7.2361 +      <entry name="horizontal_rgb" value="2" summary="horizontal RGB"/>
  7.2362 +      <entry name="horizontal_bgr" value="3" summary="horizontal BGR"/>
  7.2363 +      <entry name="vertical_rgb" value="4" summary="vertical RGB"/>
  7.2364 +      <entry name="vertical_bgr" value="5" summary="vertical BGR"/>
  7.2365 +    </enum>
  7.2366 +
  7.2367 +    <enum name="transform">
  7.2368 +      <description summary="transform from framebuffer to output">
  7.2369 +	This describes the transform that a compositor will apply to a
  7.2370 +	surface to compensate for the rotation or mirroring of an
  7.2371 +	output device.
  7.2372 +
  7.2373 +	The flipped values correspond to an initial flip around a
  7.2374 +	vertical axis followed by rotation.
  7.2375 +
  7.2376 +	The purpose is mainly to allow clients to render accordingly and
  7.2377 +	tell the compositor, so that for fullscreen surfaces, the
  7.2378 +	compositor will still be able to scan out directly from client
  7.2379 +	surfaces.
  7.2380 +      </description>
  7.2381 +      <entry name="normal" value="0" summary="no transform"/>
  7.2382 +      <entry name="90" value="1" summary="90 degrees counter-clockwise"/>
  7.2383 +      <entry name="180" value="2" summary="180 degrees counter-clockwise"/>
  7.2384 +      <entry name="270" value="3" summary="270 degrees counter-clockwise"/>
  7.2385 +      <entry name="flipped" value="4" summary="180 degree flip around a vertical axis"/>
  7.2386 +      <entry name="flipped_90" value="5" summary="flip and rotate 90 degrees counter-clockwise"/>
  7.2387 +      <entry name="flipped_180" value="6" summary="flip and rotate 180 degrees counter-clockwise"/>
  7.2388 +      <entry name="flipped_270" value="7" summary="flip and rotate 270 degrees counter-clockwise"/>
  7.2389 +    </enum>
  7.2390 +
  7.2391 +    <event name="geometry">
  7.2392 +      <description summary="properties of the output">
  7.2393 +	The geometry event describes geometric properties of the output.
  7.2394 +	The event is sent when binding to the output object and whenever
  7.2395 +	any of the properties change.
  7.2396 +      </description>
  7.2397 +      <arg name="x" type="int"
  7.2398 +	   summary="x position within the global compositor space"/>
  7.2399 +      <arg name="y" type="int"
  7.2400 +	   summary="y position within the global compositor space"/>
  7.2401 +      <arg name="physical_width" type="int"
  7.2402 +	   summary="width in millimeters of the output"/>
  7.2403 +      <arg name="physical_height" type="int"
  7.2404 +	   summary="height in millimeters of the output"/>
  7.2405 +      <arg name="subpixel" type="int" enum="subpixel"
  7.2406 +	   summary="subpixel orientation of the output"/>
  7.2407 +      <arg name="make" type="string"
  7.2408 +	   summary="textual description of the manufacturer"/>
  7.2409 +      <arg name="model" type="string"
  7.2410 +	   summary="textual description of the model"/>
  7.2411 +      <arg name="transform" type="int" enum="transform"
  7.2412 +	   summary="transform that maps framebuffer to output"/>
  7.2413 +    </event>
  7.2414 +
  7.2415 +    <enum name="mode" bitfield="true">
  7.2416 +      <description summary="mode information">
  7.2417 +	These flags describe properties of an output mode.
  7.2418 +	They are used in the flags bitfield of the mode event.
  7.2419 +      </description>
  7.2420 +      <entry name="current" value="0x1"
  7.2421 +	     summary="indicates this is the current mode"/>
  7.2422 +      <entry name="preferred" value="0x2"
  7.2423 +	     summary="indicates this is the preferred mode"/>
  7.2424 +    </enum>
  7.2425 +
  7.2426 +    <event name="mode">
  7.2427 +      <description summary="advertise available modes for the output">
  7.2428 +	The mode event describes an available mode for the output.
  7.2429 +
  7.2430 +	The event is sent when binding to the output object and there
  7.2431 +	will always be one mode, the current mode.  The event is sent
  7.2432 +	again if an output changes mode, for the mode that is now
  7.2433 +	current.  In other words, the current mode is always the last
  7.2434 +	mode that was received with the current flag set.
  7.2435 +
  7.2436 +	The size of a mode is given in physical hardware units of
  7.2437 +	the output device. This is not necessarily the same as
  7.2438 +	the output size in the global compositor space. For instance,
  7.2439 +	the output may be scaled, as described in wl_output.scale,
  7.2440 +	or transformed, as described in wl_output.transform.
  7.2441 +      </description>
  7.2442 +      <arg name="flags" type="uint" enum="mode" summary="bitfield of mode flags"/>
  7.2443 +      <arg name="width" type="int" summary="width of the mode in hardware units"/>
  7.2444 +      <arg name="height" type="int" summary="height of the mode in hardware units"/>
  7.2445 +      <arg name="refresh" type="int" summary="vertical refresh rate in mHz"/>
  7.2446 +    </event>
  7.2447 +
  7.2448 +    <!-- Version 2 additions -->
  7.2449 +
  7.2450 +    <event name="done" since="2">
  7.2451 +      <description summary="sent all information about output">
  7.2452 +	This event is sent after all other properties have been
  7.2453 +	sent after binding to the output object and after any
  7.2454 +	other property changes done after that. This allows
  7.2455 +	changes to the output properties to be seen as
  7.2456 +	atomic, even if they happen via multiple events.
  7.2457 +      </description>
  7.2458 +    </event>
  7.2459 +
  7.2460 +    <event name="scale" since="2">
  7.2461 +      <description summary="output scaling properties">
  7.2462 +	This event contains scaling geometry information
  7.2463 +	that is not in the geometry event. It may be sent after
  7.2464 +	binding the output object or if the output scale changes
  7.2465 +	later. If it is not sent, the client should assume a
  7.2466 +	scale of 1.
  7.2467 +
  7.2468 +	A scale larger than 1 means that the compositor will
  7.2469 +	automatically scale surface buffers by this amount
  7.2470 +	when rendering. This is used for very high resolution
  7.2471 +	displays where applications rendering at the native
  7.2472 +	resolution would be too small to be legible.
  7.2473 +
  7.2474 +	It is intended that scaling aware clients track the
  7.2475 +	current output of a surface, and if it is on a scaled
  7.2476 +	output it should use wl_surface.set_buffer_scale with
  7.2477 +	the scale of the output. That way the compositor can
  7.2478 +	avoid scaling the surface, and the client can supply
  7.2479 +	a higher detail image.
  7.2480 +      </description>
  7.2481 +      <arg name="factor" type="int" summary="scaling factor of output"/>
  7.2482 +    </event>
  7.2483 +
  7.2484 +    <!-- Version 3 additions -->
  7.2485 +
  7.2486 +    <request name="release" type="destructor" since="3">
  7.2487 +      <description summary="release the output object">
  7.2488 +	Using this request a client can tell the server that it is not going to
  7.2489 +	use the output object anymore.
  7.2490 +      </description>
  7.2491 +    </request>
  7.2492 +  </interface>
  7.2493 +
  7.2494 +  <interface name="wl_region" version="1">
  7.2495 +    <description summary="region interface">
  7.2496 +      A region object describes an area.
  7.2497 +
  7.2498 +      Region objects are used to describe the opaque and input
  7.2499 +      regions of a surface.
  7.2500 +    </description>
  7.2501 +
  7.2502 +    <request name="destroy" type="destructor">
  7.2503 +      <description summary="destroy region">
  7.2504 +	Destroy the region.  This will invalidate the object ID.
  7.2505 +      </description>
  7.2506 +    </request>
  7.2507 +
  7.2508 +    <request name="add">
  7.2509 +      <description summary="add rectangle to region">
  7.2510 +	Add the specified rectangle to the region.
  7.2511 +      </description>
  7.2512 +      <arg name="x" type="int" summary="region-local x coordinate"/>
  7.2513 +      <arg name="y" type="int" summary="region-local y coordinate"/>
  7.2514 +      <arg name="width" type="int" summary="rectangle width"/>
  7.2515 +      <arg name="height" type="int" summary="rectangle height"/>
  7.2516 +    </request>
  7.2517 +
  7.2518 +    <request name="subtract">
  7.2519 +      <description summary="subtract rectangle from region">
  7.2520 +	Subtract the specified rectangle from the region.
  7.2521 +      </description>
  7.2522 +      <arg name="x" type="int" summary="region-local x coordinate"/>
  7.2523 +      <arg name="y" type="int" summary="region-local y coordinate"/>
  7.2524 +      <arg name="width" type="int" summary="rectangle width"/>
  7.2525 +      <arg name="height" type="int" summary="rectangle height"/>
  7.2526 +    </request>
  7.2527 +  </interface>
  7.2528 +
  7.2529 +  <interface name="wl_subcompositor" version="1">
  7.2530 +    <description summary="sub-surface compositing">
  7.2531 +      The global interface exposing sub-surface compositing capabilities.
  7.2532 +      A wl_surface, that has sub-surfaces associated, is called the
  7.2533 +      parent surface. Sub-surfaces can be arbitrarily nested and create
  7.2534 +      a tree of sub-surfaces.
  7.2535 +
  7.2536 +      The root surface in a tree of sub-surfaces is the main
  7.2537 +      surface. The main surface cannot be a sub-surface, because
  7.2538 +      sub-surfaces must always have a parent.
  7.2539 +
  7.2540 +      A main surface with its sub-surfaces forms a (compound) window.
  7.2541 +      For window management purposes, this set of wl_surface objects is
  7.2542 +      to be considered as a single window, and it should also behave as
  7.2543 +      such.
  7.2544 +
  7.2545 +      The aim of sub-surfaces is to offload some of the compositing work
  7.2546 +      within a window from clients to the compositor. A prime example is
  7.2547 +      a video player with decorations and video in separate wl_surface
  7.2548 +      objects. This should allow the compositor to pass YUV video buffer
  7.2549 +      processing to dedicated overlay hardware when possible.
  7.2550 +    </description>
  7.2551 +
  7.2552 +    <request name="destroy" type="destructor">
  7.2553 +      <description summary="unbind from the subcompositor interface">
  7.2554 +	Informs the server that the client will not be using this
  7.2555 +	protocol object anymore. This does not affect any other
  7.2556 +	objects, wl_subsurface objects included.
  7.2557 +      </description>
  7.2558 +    </request>
  7.2559 +
  7.2560 +    <enum name="error">
  7.2561 +      <entry name="bad_surface" value="0"
  7.2562 +	     summary="the to-be sub-surface is invalid"/>
  7.2563 +    </enum>
  7.2564 +
  7.2565 +    <request name="get_subsurface">
  7.2566 +      <description summary="give a surface the role sub-surface">
  7.2567 +	Create a sub-surface interface for the given surface, and
  7.2568 +	associate it with the given parent surface. This turns a
  7.2569 +	plain wl_surface into a sub-surface.
  7.2570 +
  7.2571 +	The to-be sub-surface must not already have another role, and it
  7.2572 +	must not have an existing wl_subsurface object. Otherwise a protocol
  7.2573 +	error is raised.
  7.2574 +      </description>
  7.2575 +      <arg name="id" type="new_id" interface="wl_subsurface"
  7.2576 +	   summary="the new sub-surface object ID"/>
  7.2577 +      <arg name="surface" type="object" interface="wl_surface"
  7.2578 +	   summary="the surface to be turned into a sub-surface"/>
  7.2579 +      <arg name="parent" type="object" interface="wl_surface"
  7.2580 +	   summary="the parent surface"/>
  7.2581 +    </request>
  7.2582 +  </interface>
  7.2583 +
  7.2584 +  <interface name="wl_subsurface" version="1">
  7.2585 +    <description summary="sub-surface interface to a wl_surface">
  7.2586 +      An additional interface to a wl_surface object, which has been
  7.2587 +      made a sub-surface. A sub-surface has one parent surface. A
  7.2588 +      sub-surface's size and position are not limited to that of the parent.
  7.2589 +      Particularly, a sub-surface is not automatically clipped to its
  7.2590 +      parent's area.
  7.2591 +
  7.2592 +      A sub-surface becomes mapped, when a non-NULL wl_buffer is applied
  7.2593 +      and the parent surface is mapped. The order of which one happens
  7.2594 +      first is irrelevant. A sub-surface is hidden if the parent becomes
  7.2595 +      hidden, or if a NULL wl_buffer is applied. These rules apply
  7.2596 +      recursively through the tree of surfaces.
  7.2597 +
  7.2598 +      The behaviour of a wl_surface.commit request on a sub-surface
  7.2599 +      depends on the sub-surface's mode. The possible modes are
  7.2600 +      synchronized and desynchronized, see methods
  7.2601 +      wl_subsurface.set_sync and wl_subsurface.set_desync. Synchronized
  7.2602 +      mode caches the wl_surface state to be applied when the parent's
  7.2603 +      state gets applied, and desynchronized mode applies the pending
  7.2604 +      wl_surface state directly. A sub-surface is initially in the
  7.2605 +      synchronized mode.
  7.2606 +
  7.2607 +      Sub-surfaces have also other kind of state, which is managed by
  7.2608 +      wl_subsurface requests, as opposed to wl_surface requests. This
  7.2609 +      state includes the sub-surface position relative to the parent
  7.2610 +      surface (wl_subsurface.set_position), and the stacking order of
  7.2611 +      the parent and its sub-surfaces (wl_subsurface.place_above and
  7.2612 +      .place_below). This state is applied when the parent surface's
  7.2613 +      wl_surface state is applied, regardless of the sub-surface's mode.
  7.2614 +      As the exception, set_sync and set_desync are effective immediately.
  7.2615 +
  7.2616 +      The main surface can be thought to be always in desynchronized mode,
  7.2617 +      since it does not have a parent in the sub-surfaces sense.
  7.2618 +
  7.2619 +      Even if a sub-surface is in desynchronized mode, it will behave as
  7.2620 +      in synchronized mode, if its parent surface behaves as in
  7.2621 +      synchronized mode. This rule is applied recursively throughout the
  7.2622 +      tree of surfaces. This means, that one can set a sub-surface into
  7.2623 +      synchronized mode, and then assume that all its child and grand-child
  7.2624 +      sub-surfaces are synchronized, too, without explicitly setting them.
  7.2625 +
  7.2626 +      If the wl_surface associated with the wl_subsurface is destroyed, the
  7.2627 +      wl_subsurface object becomes inert. Note, that destroying either object
  7.2628 +      takes effect immediately. If you need to synchronize the removal
  7.2629 +      of a sub-surface to the parent surface update, unmap the sub-surface
  7.2630 +      first by attaching a NULL wl_buffer, update parent, and then destroy
  7.2631 +      the sub-surface.
  7.2632 +
  7.2633 +      If the parent wl_surface object is destroyed, the sub-surface is
  7.2634 +      unmapped.
  7.2635 +    </description>
  7.2636 +
  7.2637 +    <request name="destroy" type="destructor">
  7.2638 +      <description summary="remove sub-surface interface">
  7.2639 +	The sub-surface interface is removed from the wl_surface object
  7.2640 +	that was turned into a sub-surface with a
  7.2641 +	wl_subcompositor.get_subsurface request. The wl_surface's association
  7.2642 +	to the parent is deleted, and the wl_surface loses its role as
  7.2643 +	a sub-surface. The wl_surface is unmapped.
  7.2644 +      </description>
  7.2645 +    </request>
  7.2646 +
  7.2647 +    <enum name="error">
  7.2648 +      <entry name="bad_surface" value="0"
  7.2649 +	     summary="wl_surface is not a sibling or the parent"/>
  7.2650 +    </enum>
  7.2651 +
  7.2652 +    <request name="set_position">
  7.2653 +      <description summary="reposition the sub-surface">
  7.2654 +	This schedules a sub-surface position change.
  7.2655 +	The sub-surface will be moved so that its origin (top left
  7.2656 +	corner pixel) will be at the location x, y of the parent surface
  7.2657 +	coordinate system. The coordinates are not restricted to the parent
  7.2658 +	surface area. Negative values are allowed.
  7.2659 +
  7.2660 +	The scheduled coordinates will take effect whenever the state of the
  7.2661 +	parent surface is applied. When this happens depends on whether the
  7.2662 +	parent surface is in synchronized mode or not. See
  7.2663 +	wl_subsurface.set_sync and wl_subsurface.set_desync for details.
  7.2664 +
  7.2665 +	If more than one set_position request is invoked by the client before
  7.2666 +	the commit of the parent surface, the position of a new request always
  7.2667 +	replaces the scheduled position from any previous request.
  7.2668 +
  7.2669 +	The initial position is 0, 0.
  7.2670 +      </description>
  7.2671 +      <arg name="x" type="int" summary="x coordinate in the parent surface"/>
  7.2672 +      <arg name="y" type="int" summary="y coordinate in the parent surface"/>
  7.2673 +    </request>
  7.2674 +
  7.2675 +    <request name="place_above">
  7.2676 +      <description summary="restack the sub-surface">
  7.2677 +	This sub-surface is taken from the stack, and put back just
  7.2678 +	above the reference surface, changing the z-order of the sub-surfaces.
  7.2679 +	The reference surface must be one of the sibling surfaces, or the
  7.2680 +	parent surface. Using any other surface, including this sub-surface,
  7.2681 +	will cause a protocol error.
  7.2682 +
  7.2683 +	The z-order is double-buffered. Requests are handled in order and
  7.2684 +	applied immediately to a pending state. The final pending state is
  7.2685 +	copied to the active state the next time the state of the parent
  7.2686 +	surface is applied. When this happens depends on whether the parent
  7.2687 +	surface is in synchronized mode or not. See wl_subsurface.set_sync and
  7.2688 +	wl_subsurface.set_desync for details.
  7.2689 +
  7.2690 +	A new sub-surface is initially added as the top-most in the stack
  7.2691 +	of its siblings and parent.
  7.2692 +      </description>
  7.2693 +      <arg name="sibling" type="object" interface="wl_surface"
  7.2694 +	   summary="the reference surface"/>
  7.2695 +    </request>
  7.2696 +
  7.2697 +    <request name="place_below">
  7.2698 +      <description summary="restack the sub-surface">
  7.2699 +	The sub-surface is placed just below the reference surface.
  7.2700 +	See wl_subsurface.place_above.
  7.2701 +      </description>
  7.2702 +      <arg name="sibling" type="object" interface="wl_surface"
  7.2703 +	   summary="the reference surface"/>
  7.2704 +    </request>
  7.2705 +
  7.2706 +    <request name="set_sync">
  7.2707 +      <description summary="set sub-surface to synchronized mode">
  7.2708 +	Change the commit behaviour of the sub-surface to synchronized
  7.2709 +	mode, also described as the parent dependent mode.
  7.2710 +
  7.2711 +	In synchronized mode, wl_surface.commit on a sub-surface will
  7.2712 +	accumulate the committed state in a cache, but the state will
  7.2713 +	not be applied and hence will not change the compositor output.
  7.2714 +	The cached state is applied to the sub-surface immediately after
  7.2715 +	the parent surface's state is applied. This ensures atomic
  7.2716 +	updates of the parent and all its synchronized sub-surfaces.
  7.2717 +	Applying the cached state will invalidate the cache, so further
  7.2718 +	parent surface commits do not (re-)apply old state.
  7.2719 +
  7.2720 +	See wl_subsurface for the recursive effect of this mode.
  7.2721 +      </description>
  7.2722 +    </request>
  7.2723 +
  7.2724 +    <request name="set_desync">
  7.2725 +      <description summary="set sub-surface to desynchronized mode">
  7.2726 +	Change the commit behaviour of the sub-surface to desynchronized
  7.2727 +	mode, also described as independent or freely running mode.
  7.2728 +
  7.2729 +	In desynchronized mode, wl_surface.commit on a sub-surface will
  7.2730 +	apply the pending state directly, without caching, as happens
  7.2731 +	normally with a wl_surface. Calling wl_surface.commit on the
  7.2732 +	parent surface has no effect on the sub-surface's wl_surface
  7.2733 +	state. This mode allows a sub-surface to be updated on its own.
  7.2734 +
  7.2735 +	If cached state exists when wl_surface.commit is called in
  7.2736 +	desynchronized mode, the pending state is added to the cached
  7.2737 +	state, and applied as a whole. This invalidates the cache.
  7.2738 +
  7.2739 +	Note: even if a sub-surface is set to desynchronized, a parent
  7.2740 +	sub-surface may override it to behave as synchronized. For details,
  7.2741 +	see wl_subsurface.
  7.2742 +
  7.2743 +	If a surface's parent surface behaves as desynchronized, then
  7.2744 +	the cached state is applied on set_desync.
  7.2745 +      </description>
  7.2746 +    </request>
  7.2747 +  </interface>
  7.2748 +
  7.2749 +</protocol>
     8.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     8.2 +++ b/wayland-protocols/xdg-shell-unstable-v6.xml	Mon Jun 25 09:37:25 2018 -0700
     8.3 @@ -0,0 +1,1044 @@
     8.4 +<?xml version="1.0" encoding="UTF-8"?>
     8.5 +<protocol name="xdg_shell_unstable_v6">
     8.6 +
     8.7 +  <copyright>
     8.8 +    Copyright © 2008-2013 Kristian Høgsberg
     8.9 +    Copyright © 2013      Rafael Antognolli
    8.10 +    Copyright © 2013      Jasper St. Pierre
    8.11 +    Copyright © 2010-2013 Intel Corporation
    8.12 +
    8.13 +    Permission is hereby granted, free of charge, to any person obtaining a
    8.14 +    copy of this software and associated documentation files (the "Software"),
    8.15 +    to deal in the Software without restriction, including without limitation
    8.16 +    the rights to use, copy, modify, merge, publish, distribute, sublicense,
    8.17 +    and/or sell copies of the Software, and to permit persons to whom the
    8.18 +    Software is furnished to do so, subject to the following conditions:
    8.19 +
    8.20 +    The above copyright notice and this permission notice (including the next
    8.21 +    paragraph) shall be included in all copies or substantial portions of the
    8.22 +    Software.
    8.23 +
    8.24 +    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    8.25 +    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    8.26 +    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
    8.27 +    THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
    8.28 +    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
    8.29 +    FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
    8.30 +    DEALINGS IN THE SOFTWARE.
    8.31 +  </copyright>
    8.32 +
    8.33 +  <interface name="zxdg_shell_v6" version="1">
    8.34 +    <description summary="create desktop-style surfaces">
    8.35 +      xdg_shell allows clients to turn a wl_surface into a "real window"
    8.36 +      which can be dragged, resized, stacked, and moved around by the
    8.37 +      user. Everything about this interface is suited towards traditional
    8.38 +      desktop environments.
    8.39 +    </description>
    8.40 +
    8.41 +    <enum name="error">
    8.42 +      <entry name="role" value="0" summary="given wl_surface has another role"/>
    8.43 +      <entry name="defunct_surfaces" value="1"
    8.44 +	     summary="xdg_shell was destroyed before children"/>
    8.45 +      <entry name="not_the_topmost_popup" value="2"
    8.46 +	     summary="the client tried to map or destroy a non-topmost popup"/>
    8.47 +      <entry name="invalid_popup_parent" value="3"
    8.48 +	     summary="the client specified an invalid popup parent surface"/>
    8.49 +      <entry name="invalid_surface_state" value="4"
    8.50 +	     summary="the client provided an invalid surface state"/>
    8.51 +      <entry name="invalid_positioner" value="5"
    8.52 +	     summary="the client provided an invalid positioner"/>
    8.53 +    </enum>
    8.54 +
    8.55 +    <request name="destroy" type="destructor">
    8.56 +      <description summary="destroy xdg_shell">
    8.57 +	Destroy this xdg_shell object.
    8.58 +
    8.59 +	Destroying a bound xdg_shell object while there are surfaces
    8.60 +	still alive created by this xdg_shell object instance is illegal
    8.61 +	and will result in a protocol error.
    8.62 +      </description>
    8.63 +    </request>
    8.64 +
    8.65 +    <request name="create_positioner">
    8.66 +      <description summary="create a positioner object">
    8.67 +	Create a positioner object. A positioner object is used to position
    8.68 +	surfaces relative to some parent surface. See the interface description
    8.69 +	and xdg_surface.get_popup for details.
    8.70 +      </description>
    8.71 +      <arg name="id" type="new_id" interface="zxdg_positioner_v6"/>
    8.72 +    </request>
    8.73 +
    8.74 +    <request name="get_xdg_surface">
    8.75 +      <description summary="create a shell surface from a surface">
    8.76 +	This creates an xdg_surface for the given surface. While xdg_surface
    8.77 +	itself is not a role, the corresponding surface may only be assigned
    8.78 +	a role extending xdg_surface, such as xdg_toplevel or xdg_popup.
    8.79 +
    8.80 +	This creates an xdg_surface for the given surface. An xdg_surface is
    8.81 +	used as basis to define a role to a given surface, such as xdg_toplevel
    8.82 +	or xdg_popup. It also manages functionality shared between xdg_surface
    8.83 +	based surface roles.
    8.84 +
    8.85 +	See the documentation of xdg_surface for more details about what an
    8.86 +	xdg_surface is and how it is used.
    8.87 +      </description>
    8.88 +      <arg name="id" type="new_id" interface="zxdg_surface_v6"/>
    8.89 +      <arg name="surface" type="object" interface="wl_surface"/>
    8.90 +    </request>
    8.91 +
    8.92 +    <request name="pong">
    8.93 +      <description summary="respond to a ping event">
    8.94 +	A client must respond to a ping event with a pong request or
    8.95 +	the client may be deemed unresponsive. See xdg_shell.ping.
    8.96 +      </description>
    8.97 +      <arg name="serial" type="uint" summary="serial of the ping event"/>
    8.98 +    </request>
    8.99 +
   8.100 +    <event name="ping">
   8.101 +      <description summary="check if the client is alive">
   8.102 +	The ping event asks the client if it's still alive. Pass the
   8.103 +	serial specified in the event back to the compositor by sending
   8.104 +	a "pong" request back with the specified serial. See xdg_shell.ping.
   8.105 +
   8.106 +	Compositors can use this to determine if the client is still
   8.107 +	alive. It's unspecified what will happen if the client doesn't
   8.108 +	respond to the ping request, or in what timeframe. Clients should
   8.109 +	try to respond in a reasonable amount of time.
   8.110 +
   8.111 +	A compositor is free to ping in any way it wants, but a client must
   8.112 +	always respond to any xdg_shell object it created.
   8.113 +      </description>
   8.114 +      <arg name="serial" type="uint" summary="pass this to the pong request"/>
   8.115 +    </event>
   8.116 +  </interface>
   8.117 +
   8.118 +  <interface name="zxdg_positioner_v6" version="1">
   8.119 +    <description summary="child surface positioner">
   8.120 +      The xdg_positioner provides a collection of rules for the placement of a
   8.121 +      child surface relative to a parent surface. Rules can be defined to ensure
   8.122 +      the child surface remains within the visible area's borders, and to
   8.123 +      specify how the child surface changes its position, such as sliding along
   8.124 +      an axis, or flipping around a rectangle. These positioner-created rules are
   8.125 +      constrained by the requirement that a child surface must intersect with or
   8.126 +      be at least partially adjacent to its parent surface.
   8.127 +
   8.128 +      See the various requests for details about possible rules.
   8.129 +
   8.130 +      At the time of the request, the compositor makes a copy of the rules
   8.131 +      specified by the xdg_positioner. Thus, after the request is complete the
   8.132 +      xdg_positioner object can be destroyed or reused; further changes to the
   8.133 +      object will have no effect on previous usages.
   8.134 +
   8.135 +      For an xdg_positioner object to be considered complete, it must have a
   8.136 +      non-zero size set by set_size, and a non-zero anchor rectangle set by
   8.137 +      set_anchor_rect. Passing an incomplete xdg_positioner object when
   8.138 +      positioning a surface raises an error.
   8.139 +    </description>
   8.140 +
   8.141 +    <enum name="error">
   8.142 +      <entry name="invalid_input" value="0" summary="invalid input provided"/>
   8.143 +    </enum>
   8.144 +
   8.145 +    <request name="destroy" type="destructor">
   8.146 +      <description summary="destroy the xdg_positioner object">
   8.147 +	Notify the compositor that the xdg_positioner will no longer be used.
   8.148 +      </description>
   8.149 +    </request>
   8.150 +
   8.151 +    <request name="set_size">
   8.152 +      <description summary="set the size of the to-be positioned rectangle">
   8.153 +	Set the size of the surface that is to be positioned with the positioner
   8.154 +	object. The size is in surface-local coordinates and corresponds to the
   8.155 +	window geometry. See xdg_surface.set_window_geometry.
   8.156 +
   8.157 +	If a zero or negative size is set the invalid_input error is raised.
   8.158 +      </description>
   8.159 +      <arg name="width" type="int" summary="width of positioned rectangle"/>
   8.160 +      <arg name="height" type="int" summary="height of positioned rectangle"/>
   8.161 +    </request>
   8.162 +
   8.163 +    <request name="set_anchor_rect">
   8.164 +      <description summary="set the anchor rectangle within the parent surface">
   8.165 +	Specify the anchor rectangle within the parent surface that the child
   8.166 +	surface will be placed relative to. The rectangle is relative to the
   8.167 +	window geometry as defined by xdg_surface.set_window_geometry of the
   8.168 +	parent surface. The rectangle must be at least 1x1 large.
   8.169 +
   8.170 +	When the xdg_positioner object is used to position a child surface, the
   8.171 +	anchor rectangle may not extend outside the window geometry of the
   8.172 +	positioned child's parent surface.
   8.173 +
   8.174 +	If a zero or negative size is set the invalid_input error is raised.
   8.175 +      </description>
   8.176 +      <arg name="x" type="int" summary="x position of anchor rectangle"/>
   8.177 +      <arg name="y" type="int" summary="y position of anchor rectangle"/>
   8.178 +      <arg name="width" type="int" summary="width of anchor rectangle"/>
   8.179 +      <arg name="height" type="int" summary="height of anchor rectangle"/>
   8.180 +    </request>
   8.181 +
   8.182 +    <enum name="anchor" bitfield="true">
   8.183 +      <entry name="none" value="0"
   8.184 +	     summary="the center of the anchor rectangle"/>
   8.185 +      <entry name="top" value="1"
   8.186 +	     summary="the top edge of the anchor rectangle"/>
   8.187 +      <entry name="bottom" value="2"
   8.188 +	     summary="the bottom edge of the anchor rectangle"/>
   8.189 +      <entry name="left" value="4"
   8.190 +	     summary="the left edge of the anchor rectangle"/>
   8.191 +      <entry name="right" value="8"
   8.192 +	     summary="the right edge of the anchor rectangle"/>
   8.193 +    </enum>
   8.194 +
   8.195 +    <request name="set_anchor">
   8.196 +      <description summary="set anchor rectangle anchor edges">
   8.197 +	Defines a set of edges for the anchor rectangle. These are used to
   8.198 +	derive an anchor point that the child surface will be positioned
   8.199 +	relative to. If two orthogonal edges are specified (e.g. 'top' and
   8.200 +	'left'), then the anchor point will be the intersection of the edges
   8.201 +	(e.g. the top left position of the rectangle); otherwise, the derived
   8.202 +	anchor point will be centered on the specified edge, or in the center of
   8.203 +	the anchor rectangle if no edge is specified.
   8.204 +
   8.205 +	If two parallel anchor edges are specified (e.g. 'left' and 'right'),
   8.206 +	the invalid_input error is raised.
   8.207 +      </description>
   8.208 +      <arg name="anchor" type="uint" enum="anchor"
   8.209 +	   summary="bit mask of anchor edges"/>
   8.210 +    </request>
   8.211 +
   8.212 +    <enum name="gravity" bitfield="true">
   8.213 +      <entry name="none" value="0"
   8.214 +	     summary="center over the anchor edge"/>
   8.215 +      <entry name="top" value="1"
   8.216 +	     summary="position above the anchor edge"/>
   8.217 +      <entry name="bottom" value="2"
   8.218 +	     summary="position below the anchor edge"/>
   8.219 +      <entry name="left" value="4"
   8.220 +	     summary="position to the left of the anchor edge"/>
   8.221 +      <entry name="right" value="8"
   8.222 +	     summary="position to the right of the anchor edge"/>
   8.223 +    </enum>
   8.224 +
   8.225 +    <request name="set_gravity">
   8.226 +      <description summary="set child surface gravity">
   8.227 +	Defines in what direction a surface should be positioned, relative to
   8.228 +	the anchor point of the parent surface. If two orthogonal gravities are
   8.229 +	specified (e.g. 'bottom' and 'right'), then the child surface will be
   8.230 +	placed in the specified direction; otherwise, the child surface will be
   8.231 +	centered over the anchor point on any axis that had no gravity
   8.232 +	specified.
   8.233 +
   8.234 +	If two parallel gravities are specified (e.g. 'left' and 'right'), the
   8.235 +	invalid_input error is raised.
   8.236 +      </description>
   8.237 +      <arg name="gravity" type="uint" enum="gravity"
   8.238 +	   summary="bit mask of gravity directions"/>
   8.239 +    </request>
   8.240 +
   8.241 +    <enum name="constraint_adjustment" bitfield="true">
   8.242 +      <description summary="constraint adjustments">
   8.243 +	The constraint adjustment value define ways the compositor will adjust
   8.244 +	the position of the surface, if the unadjusted position would result
   8.245 +	in the surface being partly constrained.
   8.246 +
   8.247 +	Whether a surface is considered 'constrained' is left to the compositor
   8.248 +	to determine. For example, the surface may be partly outside the
   8.249 +	compositor's defined 'work area', thus necessitating the child surface's
   8.250 +	position be adjusted until it is entirely inside the work area.
   8.251 +
   8.252 +	The adjustments can be combined, according to a defined precedence: 1)
   8.253 +	Flip, 2) Slide, 3) Resize.
   8.254 +      </description>
   8.255 +      <entry name="none" value="0">
   8.256 +	<description summary="don't move the child surface when constrained">
   8.257 +	  Don't alter the surface position even if it is constrained on some
   8.258 +	  axis, for example partially outside the edge of a monitor.
   8.259 +	</description>
   8.260 +      </entry>
   8.261 +      <entry name="slide_x" value="1">
   8.262 +	<description summary="move along the x axis until unconstrained">
   8.263 +	  Slide the surface along the x axis until it is no longer constrained.
   8.264 +
   8.265 +	  First try to slide towards the direction of the gravity on the x axis
   8.266 +	  until either the edge in the opposite direction of the gravity is
   8.267 +	  unconstrained or the edge in the direction of the gravity is
   8.268 +	  constrained.
   8.269 +
   8.270 +	  Then try to slide towards the opposite direction of the gravity on the
   8.271 +	  x axis until either the edge in the direction of the gravity is
   8.272 +	  unconstrained or the edge in the opposite direction of the gravity is
   8.273 +	  constrained.
   8.274 +	</description>
   8.275 +      </entry>
   8.276 +      <entry name="slide_y" value="2">
   8.277 +	<description summary="move along the y axis until unconstrained">
   8.278 +	  Slide the surface along the y axis until it is no longer constrained.
   8.279 +
   8.280 +	  First try to slide towards the direction of the gravity on the y axis
   8.281 +	  until either the edge in the opposite direction of the gravity is
   8.282 +	  unconstrained or the edge in the direction of the gravity is
   8.283 +	  constrained.
   8.284 +
   8.285 +	  Then try to slide towards the opposite direction of the gravity on the
   8.286 +	  y axis until either the edge in the direction of the gravity is
   8.287 +	  unconstrained or the edge in the opposite direction of the gravity is
   8.288 +	  constrained.
   8.289 +	</description>
   8.290 +      </entry>
   8.291 +      <entry name="flip_x" value="4">
   8.292 +	<description summary="invert the anchor and gravity on the x axis">
   8.293 +	  Invert the anchor and gravity on the x axis if the surface is
   8.294 +	  constrained on the x axis. For example, if the left edge of the
   8.295 +	  surface is constrained, the gravity is 'left' and the anchor is
   8.296 +	  'left', change the gravity to 'right' and the anchor to 'right'.
   8.297 +
   8.298 +	  If the adjusted position also ends up being constrained, the resulting
   8.299 +	  position of the flip_x adjustment will be the one before the
   8.300 +	  adjustment.
   8.301 +	</description>
   8.302 +      </entry>
   8.303 +      <entry name="flip_y" value="8">
   8.304 +	<description summary="invert the anchor and gravity on the y axis">
   8.305 +	  Invert the anchor and gravity on the y axis if the surface is
   8.306 +	  constrained on the y axis. For example, if the bottom edge of the
   8.307 +	  surface is constrained, the gravity is 'bottom' and the anchor is
   8.308 +	  'bottom', change the gravity to 'top' and the anchor to 'top'.
   8.309 +
   8.310 +	  If the adjusted position also ends up being constrained, the resulting
   8.311 +	  position of the flip_y adjustment will be the one before the
   8.312 +	  adjustment.
   8.313 +	</description>
   8.314 +      </entry>
   8.315 +      <entry name="resize_x" value="16">
   8.316 +	<description summary="horizontally resize the surface">
   8.317 +	  Resize the surface horizontally so that it is completely
   8.318 +	  unconstrained.
   8.319 +	</description>
   8.320 +      </entry>
   8.321 +      <entry name="resize_y" value="32">
   8.322 +	<description summary="vertically resize the surface">
   8.323 +	  Resize the surface vertically so that it is completely unconstrained.
   8.324 +	</description>
   8.325 +      </entry>
   8.326 +    </enum>
   8.327 +
   8.328 +    <request name="set_constraint_adjustment">
   8.329 +      <description summary="set the adjustment to be done when constrained">
   8.330 +	Specify how the window should be positioned if the originally intended
   8.331 +	position caused the surface to be constrained, meaning at least
   8.332 +	partially outside positioning boundaries set by the compositor. The
   8.333 +	adjustment is set by constructing a bitmask describing the adjustment to
   8.334 +	be made when the surface is constrained on that axis.
   8.335 +
   8.336 +	If no bit for one axis is set, the compositor will assume that the child
   8.337 +	surface should not change its position on that axis when constrained.
   8.338 +
   8.339 +	If more than one bit for one axis is set, the order of how adjustments
   8.340 +	are applied is specified in the corresponding adjustment descriptions.
   8.341 +
   8.342 +	The default adjustment is none.
   8.343 +      </description>
   8.344 +      <arg name="constraint_adjustment" type="uint"
   8.345 +	   summary="bit mask of constraint adjustments"/>
   8.346 +    </request>
   8.347 +
   8.348 +    <request name="set_offset">
   8.349 +      <description summary="set surface position offset">
   8.350 +	Specify the surface position offset relative to the position of the
   8.351 +	anchor on the anchor rectangle and the anchor on the surface. For
   8.352 +	example if the anchor of the anchor rectangle is at (x, y), the surface
   8.353 +	has the gravity bottom|right, and the offset is (ox, oy), the calculated
   8.354 +	surface position will be (x + ox, y + oy). The offset position of the
   8.355 +	surface is the one used for constraint testing. See
   8.356 +	set_constraint_adjustment.
   8.357 +
   8.358 +	An example use case is placing a popup menu on top of a user interface
   8.359 +	element, while aligning the user interface element of the parent surface
   8.360 +	with some user interface element placed somewhere in the popup surface.
   8.361 +      </description>
   8.362 +      <arg name="x" type="int" summary="surface position x offset"/>
   8.363 +      <arg name="y" type="int" summary="surface position y offset"/>
   8.364 +    </request>
   8.365 +  </interface>
   8.366 +
   8.367 +  <interface name="zxdg_surface_v6" version="1">
   8.368 +    <description summary="desktop user interface surface base interface">
   8.369 +      An interface that may be implemented by a wl_surface, for
   8.370 +      implementations that provide a desktop-style user interface.
   8.371 +
   8.372 +      It provides a base set of functionality required to construct user
   8.373 +      interface elements requiring management by the compositor, such as
   8.374 +      toplevel windows, menus, etc. The types of functionality are split into
   8.375 +      xdg_surface roles.
   8.376 +
   8.377 +      Creating an xdg_surface does not set the role for a wl_surface. In order
   8.378 +      to map an xdg_surface, the client must create a role-specific object
   8.379 +      using, e.g., get_toplevel, get_popup. The wl_surface for any given
   8.380 +      xdg_surface can have at most one role, and may not be assigned any role
   8.381 +      not based on xdg_surface.
   8.382 +
   8.383 +      A role must be assigned before any other requests are made to the
   8.384 +      xdg_surface object.
   8.385 +
   8.386 +      The client must call wl_surface.commit on the corresponding wl_surface
   8.387 +      for the xdg_surface state to take effect.
   8.388 +
   8.389 +      Creating an xdg_surface from a wl_surface which has a buffer attached or
   8.390 +      committed is a client error, and any attempts by a client to attach or
   8.391 +      manipulate a buffer prior to the first xdg_surface.configure call must
   8.392 +      also be treated as errors.
   8.393 +
   8.394 +      For a surface to be mapped by the compositor, the following conditions
   8.395 +      must be met: (1) the client has assigned a xdg_surface based role to the
   8.396 +      surface, (2) the client has set and committed the xdg_surface state and
   8.397 +      the role dependent state to the surface and (3) the client has committed a
   8.398 +      buffer to the surface.
   8.399 +    </description>
   8.400 +
   8.401 +    <enum name="error">
   8.402 +      <entry name="not_constructed" value="1"/>
   8.403 +      <entry name="already_constructed" value="2"/>
   8.404 +      <entry name="unconfigured_buffer" value="3"/>
   8.405 +    </enum>
   8.406 +
   8.407 +    <request name="destroy" type="destructor">
   8.408 +      <description summary="destroy the xdg_surface">
   8.409 +	Destroy the xdg_surface object. An xdg_surface must only be destroyed
   8.410 +	after its role object has been destroyed.
   8.411 +      </description>
   8.412 +    </request>
   8.413 +
   8.414 +    <request name="get_toplevel">
   8.415 +      <description summary="assign the xdg_toplevel surface role">
   8.416 +	This creates an xdg_toplevel object for the given xdg_surface and gives
   8.417 +	the associated wl_surface the xdg_toplevel role.
   8.418 +
   8.419 +	See the documentation of xdg_toplevel for more details about what an
   8.420 +	xdg_toplevel is and how it is used.
   8.421 +      </description>
   8.422 +      <arg name="id" type="new_id" interface="zxdg_toplevel_v6"/>
   8.423 +    </request>
   8.424 +
   8.425 +    <request name="get_popup">
   8.426 +      <description summary="assign the xdg_popup surface role">
   8.427 +	This creates an xdg_popup object for the given xdg_surface and gives the
   8.428 +	associated wl_surface the xdg_popup role.
   8.429 +
   8.430 +	See the documentation of xdg_popup for more details about what an
   8.431 +	xdg_popup is and how it is used.
   8.432 +      </description>
   8.433 +      <arg name="id" type="new_id" interface="zxdg_popup_v6"/>
   8.434 +      <arg name="parent" type="object" interface="zxdg_surface_v6"/>
   8.435 +      <arg name="positioner" type="object" interface="zxdg_positioner_v6"/>
   8.436 +    </request>
   8.437 +
   8.438 +    <request name="set_window_geometry">
   8.439 +      <description summary="set the new window geometry">
   8.440 +	The window geometry of a surface is its "visible bounds" from the
   8.441 +	user's perspective. Client-side decorations often have invisible
   8.442 +	portions like drop-shadows which should be ignored for the
   8.443 +	purposes of aligning, placing and constraining windows.
   8.444 +
   8.445 +	The window geometry is double buffered, and will be applied at the
   8.446 +	time wl_surface.commit of the corresponding wl_surface is called.
   8.447 +
   8.448 +	Once the window geometry of the surface is set, it is not possible to
   8.449 +	unset it, and it will remain the same until set_window_geometry is
   8.450 +	called again, even if a new subsurface or buffer is attached.
   8.451 +
   8.452 +	If never set, the value is the full bounds of the surface,
   8.453 +	including any subsurfaces. This updates dynamically on every
   8.454 +	commit. This unset is meant for extremely simple clients.
   8.455 +
   8.456 +	The arguments are given in the surface-local coordinate space of
   8.457 +	the wl_surface associated with this xdg_surface.
   8.458 +
   8.459 +	The width and height must be greater than zero. Setting an invalid size
   8.460 +	will raise an error. When applied, the effective window geometry will be
   8.461 +	the set window geometry clamped to the bounding rectangle of the
   8.462 +	combined geometry of the surface of the xdg_surface and the associated
   8.463 +	subsurfaces.
   8.464 +      </description>
   8.465 +      <arg name="x" type="int"/>
   8.466 +      <arg name="y" type="int"/>
   8.467 +      <arg name="width" type="int"/>
   8.468 +      <arg name="height" type="int"/>
   8.469 +    </request>
   8.470 +
   8.471 +    <request name="ack_configure">
   8.472 +      <description summary="ack a configure event">
   8.473 +	When a configure event is received, if a client commits the
   8.474 +	surface in response to the configure event, then the client
   8.475 +	must make an ack_configure request sometime before the commit
   8.476 +	request, passing along the serial of the configure event.
   8.477 +
   8.478 +	For instance, for toplevel surfaces the compositor might use this
   8.479 +	information to move a surface to the top left only when the client has
   8.480 +	drawn itself for the maximized or fullscreen state.
   8.481 +
   8.482 +	If the client receives multiple configure events before it
   8.483 +	can respond to one, it only has to ack the last configure event.
   8.484 +
   8.485 +	A client is not required to commit immediately after sending
   8.486 +	an ack_configure request - it may even ack_configure several times
   8.487 +	before its next surface commit.
   8.488 +
   8.489 +	A client may send multiple ack_configure requests before committing, but
   8.490 +	only the last request sent before a commit indicates which configure
   8.491 +	event the client really is responding to.
   8.492 +      </description>
   8.493 +      <arg name="serial" type="uint" summary="the serial from the configure event"/>
   8.494 +    </request>
   8.495 +
   8.496 +    <event name="configure">
   8.497 +      <description summary="suggest a surface change">
   8.498 +	The configure event marks the end of a configure sequence. A configure
   8.499 +	sequence is a set of one or more events configuring the state of the
   8.500 +	xdg_surface, including the final xdg_surface.configure event.
   8.501 +
   8.502 +	Where applicable, xdg_surface surface roles will during a configure
   8.503 +	sequence extend this event as a latched state sent as events before the
   8.504 +	xdg_surface.configure event. Such events should be considered to make up
   8.505 +	a set of atomically applied configuration states, where the
   8.506 +	xdg_surface.configure commits the accumulated state.
   8.507 +
   8.508 +	Clients should arrange their surface for the new states, and then send
   8.509 +	an ack_configure request with the serial sent in this configure event at
   8.510 +	some point before committing the new surface.
   8.511 +
   8.512 +	If the client receives multiple configure events before it can respond
   8.513 +	to one, it is free to discard all but the last event it received.
   8.514 +      </description>
   8.515 +      <arg name="serial" type="uint" summary="serial of the configure event"/>
   8.516 +    </event>
   8.517 +  </interface>
   8.518 +
   8.519 +  <interface name="zxdg_toplevel_v6" version="1">
   8.520 +    <description summary="toplevel surface">
   8.521 +      This interface defines an xdg_surface role which allows a surface to,
   8.522 +      among other things, set window-like properties such as maximize,
   8.523 +      fullscreen, and minimize, set application-specific metadata like title and
   8.524 +      id, and well as trigger user interactive operations such as interactive
   8.525 +      resize and move.
   8.526 +    </description>
   8.527 +
   8.528 +    <request name="destroy" type="destructor">
   8.529 +      <description summary="destroy the xdg_toplevel">
   8.530 +	Unmap and destroy the window. The window will be effectively
   8.531 +	hidden from the user's point of view, and all state like
   8.532 +	maximization, fullscreen, and so on, will be lost.
   8.533 +      </description>
   8.534 +    </request>
   8.535 +
   8.536 +    <request name="set_parent">
   8.537 +      <description summary="set the parent of this surface">
   8.538 +	Set the "parent" of this surface. This window should be stacked
   8.539 +	above a parent. The parent surface must be mapped as long as this
   8.540 +	surface is mapped.
   8.541 +
   8.542 +	Parent windows should be set on dialogs, toolboxes, or other
   8.543 +	"auxiliary" surfaces, so that the parent is raised when the dialog
   8.544 +	is raised.
   8.545 +      </description>
   8.546 +      <arg name="parent" type="object" interface="zxdg_toplevel_v6" allow-null="true"/>
   8.547 +    </request>
   8.548 +
   8.549 +    <request name="set_title">
   8.550 +      <description summary="set surface title">
   8.551 +	Set a short title for the surface.
   8.552 +
   8.553 +	This string may be used to identify the surface in a task bar,
   8.554 +	window list, or other user interface elements provided by the
   8.555 +	compositor.
   8.556 +
   8.557 +	The string must be encoded in UTF-8.
   8.558 +      </description>
   8.559 +      <arg name="title" type="string"/>
   8.560 +    </request>
   8.561 +
   8.562 +    <request name="set_app_id">
   8.563 +      <description summary="set application ID">
   8.564 +	Set an application identifier for the surface.
   8.565 +
   8.566 +	The app ID identifies the general class of applications to which
   8.567 +	the surface belongs. The compositor can use this to group multiple
   8.568 +	surfaces together, or to determine how to launch a new application.
   8.569 +
   8.570 +	For D-Bus activatable applications, the app ID is used as the D-Bus
   8.571 +	service name.
   8.572 +
   8.573 +	The compositor shell will try to group application surfaces together
   8.574 +	by their app ID. As a best practice, it is suggested to select app
   8.575 +	ID's that match the basename of the application's .desktop file.
   8.576 +	For example, "org.freedesktop.FooViewer" where the .desktop file is
   8.577 +	"org.freedesktop.FooViewer.desktop".
   8.578 +
   8.579 +	See the desktop-entry specification [0] for more details on
   8.580 +	application identifiers and how they relate to well-known D-Bus
   8.581 +	names and .desktop files.
   8.582 +
   8.583 +	[0] http://standards.freedesktop.org/desktop-entry-spec/
   8.584 +      </description>
   8.585 +      <arg name="app_id" type="string"/>
   8.586 +    </request>
   8.587 +
   8.588 +    <request name="show_window_menu">
   8.589 +      <description summary="show the window menu">
   8.590 +	Clients implementing client-side decorations might want to show
   8.591 +	a context menu when right-clicking on the decorations, giving the
   8.592 +	user a menu that they can use to maximize or minimize the window.
   8.593 +
   8.594 +	This request asks the compositor to pop up such a window menu at
   8.595 +	the given position, relative to the local surface coordinates of
   8.596 +	the parent surface. There are no guarantees as to what menu items
   8.597 +	the window menu contains.
   8.598 +
   8.599 +	This request must be used in response to some sort of user action
   8.600 +	like a button press, key press, or touch down event.
   8.601 +      </description>
   8.602 +      <arg name="seat" type="object" interface="wl_seat" summary="the wl_seat of the user event"/>
   8.603 +      <arg name="serial" type="uint" summary="the serial of the user event"/>
   8.604 +      <arg name="x" type="int" summary="the x position to pop up the window menu at"/>
   8.605 +      <arg name="y" type="int" summary="the y position to pop up the window menu at"/>
   8.606 +    </request>
   8.607 +
   8.608 +    <request name="move">
   8.609 +      <description summary="start an interactive move">
   8.610 +	Start an interactive, user-driven move of the surface.
   8.611 +
   8.612 +	This request must be used in response to some sort of user action
   8.613 +	like a button press, key press, or touch down event. The passed
   8.614 +	serial is used to determine the type of interactive move (touch,
   8.615 +	pointer, etc).
   8.616 +
   8.617 +	The server may ignore move requests depending on the state of
   8.618 +	the surface (e.g. fullscreen or maximized), or if the passed serial
   8.619 +	is no longer valid.
   8.620 +
   8.621 +	If triggered, the surface will lose the focus of the device
   8.622 +	(wl_pointer, wl_touch, etc) used for the move. It is up to the
   8.623 +	compositor to visually indicate that the move is taking place, such as
   8.624 +	updating a pointer cursor, during the move. There is no guarantee
   8.625 +	that the device focus will return when the move is completed.
   8.626 +      </description>
   8.627 +      <arg name="seat" type="object" interface="wl_seat" summary="the wl_seat of the user event"/>
   8.628 +      <arg name="serial" type="uint" summary="the serial of the user event"/>
   8.629 +    </request>
   8.630 +
   8.631 +    <enum name="resize_edge">
   8.632 +      <description summary="edge values for resizing">
   8.633 +	These values are used to indicate which edge of a surface
   8.634 +	is being dragged in a resize operation.
   8.635 +      </description>
   8.636 +      <entry name="none" value="0"/>
   8.637 +      <entry name="top" value="1"/>
   8.638 +      <entry name="bottom" value="2"/>
   8.639 +      <entry name="left" value="4"/>
   8.640 +      <entry name="top_left" value="5"/>
   8.641 +      <entry name="bottom_left" value="6"/>
   8.642 +      <entry name="right" value="8"/>
   8.643 +      <entry name="top_right" value="9"/>
   8.644 +      <entry name="bottom_right" value="10"/>
   8.645 +    </enum>
   8.646 +
   8.647 +    <request name="resize">
   8.648 +      <description summary="start an interactive resize">
   8.649 +	Start a user-driven, interactive resize of the surface.
   8.650 +
   8.651 +	This request must be used in response to some sort of user action
   8.652 +	like a button press, key press, or touch down event. The passed
   8.653 +	serial is used to determine the type of interactive resize (touch,
   8.654 +	pointer, etc).
   8.655 +
   8.656 +	The server may ignore resize requests depending on the state of
   8.657 +	the surface (e.g. fullscreen or maximized).
   8.658 +
   8.659 +	If triggered, the client will receive configure events with the
   8.660 +	"resize" state enum value and the expected sizes. See the "resize"
   8.661 +	enum value for more details about what is required. The client
   8.662 +	must also acknowledge configure events using "ack_configure". After
   8.663 +	the resize is completed, the client will receive another "configure"
   8.664 +	event without the resize state.
   8.665 +
   8.666 +	If triggered, the surface also will lose the focus of the device
   8.667 +	(wl_pointer, wl_touch, etc) used for the resize. It is up to the
   8.668 +	compositor to visually indicate that the resize is taking place,
   8.669 +	such as updating a pointer cursor, during the resize. There is no
   8.670 +	guarantee that the device focus will return when the resize is
   8.671 +	completed.
   8.672 +
   8.673 +	The edges parameter specifies how the surface should be resized,
   8.674 +	and is one of the values of the resize_edge enum. The compositor
   8.675 +	may use this information to update the surface position for
   8.676 +	example when dragging the top left corner. The compositor may also
   8.677 +	use this information to adapt its behavior, e.g. choose an
   8.678 +	appropriate cursor image.
   8.679 +      </description>
   8.680 +      <arg name="seat" type="object" interface="wl_seat" summary="the wl_seat of the user event"/>
   8.681 +      <arg name="serial" type="uint" summary="the serial of the user event"/>
   8.682 +      <arg name="edges" type="uint" summary="which edge or corner is being dragged"/>
   8.683 +    </request>
   8.684 +
   8.685 +    <enum name="state">
   8.686 +      <description summary="types of state on the surface">
   8.687 +	The different state values used on the surface. This is designed for
   8.688 +	state values like maximized, fullscreen. It is paired with the
   8.689 +	configure event to ensure that both the client and the compositor
   8.690 +	setting the state can be synchronized.
   8.691 +
   8.692 +	States set in this way are double-buffered. They will get applied on
   8.693 +	the next commit.
   8.694 +      </description>
   8.695 +      <entry name="maximized" value="1" summary="the surface is maximized">
   8.696 +	<description summary="the surface is maximized">
   8.697 +	  The surface is maximized. The window geometry specified in the configure
   8.698 +	  event must be obeyed by the client.
   8.699 +	</description>
   8.700 +      </entry>
   8.701 +      <entry name="fullscreen" value="2" summary="the surface is fullscreen">
   8.702 +	<description summary="the surface is fullscreen">
   8.703 +	  The surface is fullscreen. The window geometry specified in the configure
   8.704 +	  event must be obeyed by the client.
   8.705 +	</description>
   8.706 +      </entry>
   8.707 +      <entry name="resizing" value="3" summary="the surface is being resized">
   8.708 +	<description summary="the surface is being resized">
   8.709 +	  The surface is being resized. The window geometry specified in the
   8.710 +	  configure event is a maximum; the client cannot resize beyond it.
   8.711 +	  Clients that have aspect ratio or cell sizing configuration can use
   8.712 +	  a smaller size, however.
   8.713 +	</description>
   8.714 +      </entry>
   8.715 +      <entry name="activated" value="4" summary="the surface is now activated">
   8.716 +	<description summary="the surface is now activated">
   8.717 +	  Client window decorations should be painted as if the window is
   8.718 +	  active. Do not assume this means that the window actually has
   8.719 +	  keyboard or pointer focus.
   8.720 +	</description>
   8.721 +      </entry>
   8.722 +    </enum>
   8.723 +
   8.724 +    <request name="set_max_size">
   8.725 +      <description summary="set the maximum size">
   8.726 +	Set a maximum size for the window.
   8.727 +
   8.728 +	The client can specify a maximum size so that the compositor does
   8.729 +	not try to configure the window beyond this size.
   8.730 +
   8.731 +	The width and height arguments are in window geometry coordinates.
   8.732 +	See xdg_surface.set_window_geometry.
   8.733 +
   8.734 +	Values set in this way are double-buffered. They will get applied
   8.735 +	on the next commit.
   8.736 +
   8.737 +	The compositor can use this information to allow or disallow
   8.738 +	different states like maximize or fullscreen and draw accurate
   8.739 +	animations.
   8.740 +
   8.741 +	Similarly, a tiling window manager may use this information to
   8.742 +	place and resize client windows in a more effective way.
   8.743 +
   8.744 +	The client should not rely on the compositor to obey the maximum
   8.745 +	size. The compositor may decide to ignore the values set by the
   8.746 +	client and request a larger size.
   8.747 +
   8.748 +	If never set, or a value of zero in the request, means that the
   8.749 +	client has no expected maximum size in the given dimension.
   8.750 +	As a result, a client wishing to reset the maximum size
   8.751 +	to an unspecified state can use zero for width and height in the
   8.752 +	request.
   8.753 +
   8.754 +	Requesting a maximum size to be smaller than the minimum size of
   8.755 +	a surface is illegal and will result in a protocol error.
   8.756 +
   8.757 +	The width and height must be greater than or equal to zero. Using
   8.758 +	strictly negative values for width and height will result in a
   8.759 +	protocol error.
   8.760 +      </description>
   8.761 +      <arg name="width" type="int"/>
   8.762 +      <arg name="height" type="int"/>
   8.763 +    </request>
   8.764 +
   8.765 +    <request name="set_min_size">
   8.766 +      <description summary="set the minimum size">
   8.767 +	Set a minimum size for the window.
   8.768 +
   8.769 +	The client can specify a minimum size so that the compositor does
   8.770 +	not try to configure the window below this size.
   8.771 +
   8.772 +	The width and height arguments are in window geometry coordinates.
   8.773 +	See xdg_surface.set_window_geometry.
   8.774 +
   8.775 +	Values set in this way are double-buffered. They will get applied
   8.776 +	on the next commit.
   8.777 +
   8.778 +	The compositor can use this information to allow or disallow
   8.779 +	different states like maximize or fullscreen and draw accurate
   8.780 +	animations.
   8.781 +
   8.782 +	Similarly, a tiling window manager may use this information to
   8.783 +	place and resize client windows in a more effective way.
   8.784 +
   8.785 +	The client should not rely on the compositor to obey the minimum
   8.786 +	size. The compositor may decide to ignore the values set by the
   8.787 +	client and request a smaller size.
   8.788 +
   8.789 +	If never set, or a value of zero in the request, means that the
   8.790 +	client has no expected minimum size in the given dimension.
   8.791 +	As a result, a client wishing to reset the minimum size
   8.792 +	to an unspecified state can use zero for width and height in the
   8.793 +	request.
   8.794 +
   8.795 +	Requesting a minimum size to be larger than the maximum size of
   8.796 +	a surface is illegal and will result in a protocol error.
   8.797 +
   8.798 +	The width and height must be greater than or equal to zero. Using
   8.799 +	strictly negative values for width and height will result in a
   8.800 +	protocol error.
   8.801 +      </description>
   8.802 +      <arg name="width" type="int"/>
   8.803 +      <arg name="height" type="int"/>
   8.804 +    </request>
   8.805 +
   8.806 +    <request name="set_maximized">
   8.807 +      <description summary="maximize the window">
   8.808 +	Maximize the surface.
   8.809 +
   8.810 +	After requesting that the surface should be maximized, the compositor
   8.811 +	will respond by emitting a configure event with the "maximized" state
   8.812 +	and the required window geometry. The client should then update its
   8.813 +	content, drawing it in a maximized state, i.e. without shadow or other
   8.814 +	decoration outside of the window geometry. The client must also
   8.815 +	acknowledge the configure when committing the new content (see
   8.816 +	ack_configure).
   8.817 +
   8.818 +	It is up to the compositor to decide how and where to maximize the
   8.819 +	surface, for example which output and what region of the screen should
   8.820 +	be used.
   8.821 +
   8.822 +	If the surface was already maximized, the compositor will still emit
   8.823 +	a configure event with the "maximized" state.
   8.824 +      </description>
   8.825 +    </request>
   8.826 +
   8.827 +    <request name="unset_maximized">
   8.828 +      <description summary="unmaximize the window">
   8.829 +	Unmaximize the surface.
   8.830 +
   8.831 +	After requesting that the surface should be unmaximized, the compositor
   8.832 +	will respond by emitting a configure event without the "maximized"
   8.833 +	state. If available, the compositor will include the window geometry
   8.834 +	dimensions the window had prior to being maximized in the configure
   8.835 +	request. The client must then update its content, drawing it in a
   8.836 +	regular state, i.e. potentially with shadow, etc. The client must also
   8.837 +	acknowledge the configure when committing the new content (see
   8.838 +	ack_configure).
   8.839 +
   8.840 +	It is up to the compositor to position the surface after it was
   8.841 +	unmaximized; usually the position the surface had before maximizing, if
   8.842 +	applicable.
   8.843 +
   8.844 +	If the surface was already not maximized, the compositor will still
   8.845 +	emit a configure event without the "maximized" state.
   8.846 +      </description>
   8.847 +    </request>
   8.848 +
   8.849 +    <request name="set_fullscreen">
   8.850 +      <description summary="set the window as fullscreen on a monitor">
   8.851 +	Make the surface fullscreen.
   8.852 +
   8.853 +	You can specify an output that you would prefer to be fullscreen.
   8.854 +	If this value is NULL, it's up to the compositor to choose which
   8.855 +	display will be used to map this surface.
   8.856 +
   8.857 +	If the surface doesn't cover the whole output, the compositor will
   8.858 +	position the surface in the center of the output and compensate with
   8.859 +	black borders filling the rest of the output.
   8.860 +      </description>
   8.861 +      <arg name="output" type="object" interface="wl_output" allow-null="true"/>
   8.862 +    </request>
   8.863 +    <request name="unset_fullscreen" />
   8.864 +
   8.865 +    <request name="set_minimized">
   8.866 +      <description summary="set the window as minimized">
   8.867 +	Request that the compositor minimize your surface. There is no
   8.868 +	way to know if the surface is currently minimized, nor is there
   8.869 +	any way to unset minimization on this surface.
   8.870 +
   8.871 +	If you are looking to throttle redrawing when minimized, please
   8.872 +	instead use the wl_surface.frame event for this, as this will
   8.873 +	also work with live previews on windows in Alt-Tab, Expose or
   8.874 +	similar compositor features.
   8.875 +      </description>
   8.876 +    </request>
   8.877 +
   8.878 +    <event name="configure">
   8.879 +      <description summary="suggest a surface change">
   8.880 +	This configure event asks the client to resize its toplevel surface or
   8.881 +	to change its state. The configured state should not be applied
   8.882 +	immediately. See xdg_surface.configure for details.
   8.883 +
   8.884 +	The width and height arguments specify a hint to the window
   8.885 +	about how its surface should be resized in window geometry
   8.886 +	coordinates. See set_window_geometry.
   8.887 +
   8.888 +	If the width or height arguments are zero, it means the client
   8.889 +	should decide its own window dimension. This may happen when the
   8.890 +	compositor needs to configure the state of the surface but doesn't
   8.891 +	have any information about any previous or expected dimension.
   8.892 +
   8.893 +	The states listed in the event specify how the width/height
   8.894 +	arguments should be interpreted, and possibly how it should be
   8.895 +	drawn.
   8.896 +
   8.897 +	Clients must send an ack_configure in response to this event. See
   8.898 +	xdg_surface.configure and xdg_surface.ack_configure for details.
   8.899 +      </description>
   8.900 +      <arg name="width" type="int"/>
   8.901 +      <arg name="height" type="int"/>
   8.902 +      <arg name="states" type="array"/>
   8.903 +    </event>
   8.904 +
   8.905 +    <event name="close">
   8.906 +      <description summary="surface wants to be closed">
   8.907 +	The close event is sent by the compositor when the user
   8.908 +	wants the surface to be closed. This should be equivalent to
   8.909 +	the user clicking the close button in client-side decorations,
   8.910 +	if your application has any.
   8.911 +
   8.912 +	This is only a request that the user intends to close the
   8.913 +	window. The client may choose to ignore this request, or show
   8.914 +	a dialog to ask the user to save their data, etc.
   8.915 +      </description>
   8.916 +    </event>
   8.917 +  </interface>
   8.918 +
   8.919 +  <interface name="zxdg_popup_v6" version="1">
   8.920 +    <description summary="short-lived, popup surfaces for menus">
   8.921 +      A popup surface is a short-lived, temporary surface. It can be used to
   8.922 +      implement for example menus, popovers, tooltips and other similar user
   8.923 +      interface concepts.
   8.924 +
   8.925 +      A popup can be made to take an explicit grab. See xdg_popup.grab for
   8.926 +      details.
   8.927 +
   8.928 +      When the popup is dismissed, a popup_done event will be sent out, and at
   8.929 +      the same time the surface will be unmapped. See the xdg_popup.popup_done
   8.930 +      event for details.
   8.931 +
   8.932 +      Explicitly destroying the xdg_popup object will also dismiss the popup and
   8.933 +      unmap the surface. Clients that want to dismiss the popup when another
   8.934 +      surface of their own is clicked should dismiss the popup using the destroy
   8.935 +      request.
   8.936 +
   8.937 +      The parent surface must have either the xdg_toplevel or xdg_popup surface
   8.938 +      role.
   8.939 +
   8.940 +      A newly created xdg_popup will be stacked on top of all previously created
   8.941 +      xdg_popup surfaces associated with the same xdg_toplevel.
   8.942 +
   8.943 +      The parent of an xdg_popup must be mapped (see the xdg_surface
   8.944 +      description) before the xdg_popup itself.
   8.945 +
   8.946 +      The x and y arguments passed when creating the popup object specify
   8.947 +      where the top left of the popup should be placed, relative to the
   8.948 +      local surface coordinates of the parent surface. See
   8.949 +      xdg_surface.get_popup. An xdg_popup must intersect with or be at least
   8.950 +      partially adjacent to its parent surface.
   8.951 +
   8.952 +      The client must call wl_surface.commit on the corresponding wl_surface
   8.953 +      for the xdg_popup state to take effect.
   8.954 +    </description>
   8.955 +
   8.956 +    <enum name="error">
   8.957 +      <entry name="invalid_grab" value="0"
   8.958 +	     summary="tried to grab after being mapped"/>
   8.959 +    </enum>
   8.960 +
   8.961 +    <request name="destroy" type="destructor">
   8.962 +      <description summary="remove xdg_popup interface">
   8.963 +	This destroys the popup. Explicitly destroying the xdg_popup
   8.964 +	object will also dismiss the popup, and unmap the surface.
   8.965 +
   8.966 +	If this xdg_popup is not the "topmost" popup, a protocol error
   8.967 +	will be sent.
   8.968 +      </description>
   8.969 +    </request>
   8.970 +
   8.971 +    <request name="grab">
   8.972 +      <description summary="make the popup take an explicit grab">
   8.973 +	This request makes the created popup take an explicit grab. An explicit
   8.974 +	grab will be dismissed when the user dismisses the popup, or when the
   8.975 +	client destroys the xdg_popup. This can be done by the user clicking
   8.976 +	outside the surface, using the keyboard, or even locking the screen
   8.977 +	through closing the lid or a timeout.
   8.978 +
   8.979 +	If the compositor denies the grab, the popup will be immediately
   8.980 +	dismissed.
   8.981 +
   8.982 +	This request must be used in response to some sort of user action like a
   8.983 +	button press, key press, or touch down event. The serial number of the
   8.984 +	event should be passed as 'serial'.
   8.985 +
   8.986 +	The parent of a grabbing popup must either be an xdg_toplevel surface or
   8.987 +	another xdg_popup with an explicit grab. If the parent is another
   8.988 +	xdg_popup it means that the popups are nested, with this popup now being
   8.989 +	the topmost popup.
   8.990 +
   8.991 +	Nested popups must be destroyed in the reverse order they were created
   8.992 +	in, e.g. the only popup you are allowed to destroy at all times is the
   8.993 +	topmost one.
   8.994 +
   8.995 +	When compositors choose to dismiss a popup, they may dismiss every
   8.996 +	nested grabbing popup as well. When a compositor dismisses popups, it
   8.997 +	will follow the same dismissing order as required from the client.
   8.998 +
   8.999 +	The parent of a grabbing popup must either be another xdg_popup with an
  8.1000 +	active explicit grab, or an xdg_popup or xdg_toplevel, if there are no
  8.1001 +	explicit grabs already taken.
  8.1002 +
  8.1003 +	If the topmost grabbing popup is destroyed, the grab will be returned to
  8.1004 +	the parent of the popup, if that parent previously had an explicit grab.
  8.1005 +
  8.1006 +	If the parent is a grabbing popup which has already been dismissed, this
  8.1007 +	popup will be immediately dismissed. If the parent is a popup that did
  8.1008 +	not take an explicit grab, an error will be raised.
  8.1009 +
  8.1010 +	During a popup grab, the client owning the grab will receive pointer
  8.1011 +	and touch events for all their surfaces as normal (similar to an
  8.1012 +	"owner-events" grab in X11 parlance), while the top most grabbing popup
  8.1013 +	will always have keyboard focus.
  8.1014 +      </description>
  8.1015 +      <arg name="seat" type="object" interface="wl_seat"
  8.1016 +	   summary="the wl_seat of the user event"/>
  8.1017 +      <arg name="serial" type="uint" summary="the serial of the user event"/>
  8.1018 +    </request>
  8.1019 +
  8.1020 +    <event name="configure">
  8.1021 +      <description summary="configure the popup surface">
  8.1022 +	This event asks the popup surface to configure itself given the
  8.1023 +	configuration. The configured state should not be applied immediately.
  8.1024 +	See xdg_surface.configure for details.
  8.1025 +
  8.1026 +	The x and y arguments represent the position the popup was placed at
  8.1027 +	given the xdg_positioner rule, relative to the upper left corner of the
  8.1028 +	window geometry of the parent surface.
  8.1029 +      </description>
  8.1030 +      <arg name="x" type="int"
  8.1031 +	   summary="x position relative to parent surface window geometry"/>
  8.1032 +      <arg name="y" type="int"
  8.1033 +	   summary="y position relative to parent surface window geometry"/>
  8.1034 +      <arg name="width" type="int" summary="window geometry width"/>
  8.1035 +      <arg name="height" type="int" summary="window geometry height"/>
  8.1036 +    </event>
  8.1037 +
  8.1038 +    <event name="popup_done">
  8.1039 +      <description summary="popup interaction is done">
  8.1040 +	The popup_done event is sent out when a popup is dismissed by the
  8.1041 +	compositor. The client should destroy the xdg_popup object at this
  8.1042 +	point.
  8.1043 +      </description>
  8.1044 +    </event>
  8.1045 +
  8.1046 +  </interface>
  8.1047 +</protocol>
     9.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     9.2 +++ b/wayland-protocols/xdg-shell.xml	Mon Jun 25 09:37:25 2018 -0700
     9.3 @@ -0,0 +1,1120 @@
     9.4 +<?xml version="1.0" encoding="UTF-8"?>
     9.5 +<protocol name="xdg_shell">
     9.6 +
     9.7 +  <copyright>
     9.8 +    Copyright © 2008-2013 Kristian Høgsberg
     9.9 +    Copyright © 2013      Rafael Antognolli
    9.10 +    Copyright © 2013      Jasper St. Pierre
    9.11 +    Copyright © 2010-2013 Intel Corporation
    9.12 +    Copyright © 2015-2017 Samsung Electronics Co., Ltd
    9.13 +    Copyright © 2015-2017 Red Hat Inc.
    9.14 +
    9.15 +    Permission is hereby granted, free of charge, to any person obtaining a
    9.16 +    copy of this software and associated documentation files (the "Software"),
    9.17 +    to deal in the Software without restriction, including without limitation
    9.18 +    the rights to use, copy, modify, merge, publish, distribute, sublicense,
    9.19 +    and/or sell copies of the Software, and to permit persons to whom the
    9.20 +    Software is furnished to do so, subject to the following conditions:
    9.21 +
    9.22 +    The above copyright notice and this permission notice (including the next
    9.23 +    paragraph) shall be included in all copies or substantial portions of the
    9.24 +    Software.
    9.25 +
    9.26 +    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    9.27 +    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    9.28 +    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
    9.29 +    THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
    9.30 +    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
    9.31 +    FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
    9.32 +    DEALINGS IN THE SOFTWARE.
    9.33 +  </copyright>
    9.34 +
    9.35 +  <interface name="xdg_wm_base" version="1">
    9.36 +    <description summary="create desktop-style surfaces">
    9.37 +      The xdg_wm_base interface is exposed as a global object enabling clients
    9.38 +      to turn their wl_surfaces into windows in a desktop environment. It
    9.39 +      defines the basic functionality needed for clients and the compositor to
    9.40 +      create windows that can be dragged, resized, maximized, etc, as well as
    9.41 +      creating transient windows such as popup menus.
    9.42 +    </description>
    9.43 +
    9.44 +    <enum name="error">
    9.45 +      <entry name="role" value="0" summary="given wl_surface has another role"/>
    9.46 +      <entry name="defunct_surfaces" value="1"
    9.47 +	     summary="xdg_wm_base was destroyed before children"/>
    9.48 +      <entry name="not_the_topmost_popup" value="2"
    9.49 +	     summary="the client tried to map or destroy a non-topmost popup"/>
    9.50 +      <entry name="invalid_popup_parent" value="3"
    9.51 +	     summary="the client specified an invalid popup parent surface"/>
    9.52 +      <entry name="invalid_surface_state" value="4"
    9.53 +	     summary="the client provided an invalid surface state"/>
    9.54 +      <entry name="invalid_positioner" value="5"
    9.55 +	     summary="the client provided an invalid positioner"/>
    9.56 +    </enum>
    9.57 +
    9.58 +    <request name="destroy" type="destructor">
    9.59 +      <description summary="destroy xdg_wm_base">
    9.60 +	Destroy this xdg_wm_base object.
    9.61 +
    9.62 +	Destroying a bound xdg_wm_base object while there are surfaces
    9.63 +	still alive created by this xdg_wm_base object instance is illegal
    9.64 +	and will result in a protocol error.
    9.65 +      </description>
    9.66 +    </request>
    9.67 +
    9.68 +    <request name="create_positioner">
    9.69 +      <description summary="create a positioner object">
    9.70 +	Create a positioner object. A positioner object is used to position
    9.71 +	surfaces relative to some parent surface. See the interface description
    9.72 +	and xdg_surface.get_popup for details.
    9.73 +      </description>
    9.74 +      <arg name="id" type="new_id" interface="xdg_positioner"/>
    9.75 +    </request>
    9.76 +
    9.77 +    <request name="get_xdg_surface">
    9.78 +      <description summary="create a shell surface from a surface">
    9.79 +	This creates an xdg_surface for the given surface. While xdg_surface
    9.80 +	itself is not a role, the corresponding surface may only be assigned
    9.81 +	a role extending xdg_surface, such as xdg_toplevel or xdg_popup.
    9.82 +
    9.83 +	This creates an xdg_surface for the given surface. An xdg_surface is
    9.84 +	used as basis to define a role to a given surface, such as xdg_toplevel
    9.85 +	or xdg_popup. It also manages functionality shared between xdg_surface
    9.86 +	based surface roles.
    9.87 +
    9.88 +	See the documentation of xdg_surface for more details about what an
    9.89 +	xdg_surface is and how it is used.
    9.90 +      </description>
    9.91 +      <arg name="id" type="new_id" interface="xdg_surface"/>
    9.92 +      <arg name="surface" type="object" interface="wl_surface"/>
    9.93 +    </request>
    9.94 +
    9.95 +    <request name="pong">
    9.96 +      <description summary="respond to a ping event">
    9.97 +	A client must respond to a ping event with a pong request or
    9.98 +	the client may be deemed unresponsive. See xdg_wm_base.ping.
    9.99 +      </description>
   9.100 +      <arg name="serial" type="uint" summary="serial of the ping event"/>
   9.101 +    </request>
   9.102 +
   9.103 +    <event name="ping">
   9.104 +      <description summary="check if the client is alive">
   9.105 +	The ping event asks the client if it's still alive. Pass the
   9.106 +	serial specified in the event back to the compositor by sending
   9.107 +	a "pong" request back with the specified serial. See xdg_wm_base.ping.
   9.108 +
   9.109 +	Compositors can use this to determine if the client is still
   9.110 +	alive. It's unspecified what will happen if the client doesn't
   9.111 +	respond to the ping request, or in what timeframe. Clients should
   9.112 +	try to respond in a reasonable amount of time.
   9.113 +
   9.114 +	A compositor is free to ping in any way it wants, but a client must
   9.115 +	always respond to any xdg_wm_base object it created.
   9.116 +      </description>
   9.117 +      <arg name="serial" type="uint" summary="pass this to the pong request"/>
   9.118 +    </event>
   9.119 +  </interface>
   9.120 +
   9.121 +  <interface name="xdg_positioner" version="1">
   9.122 +    <description summary="child surface positioner">
   9.123 +      The xdg_positioner provides a collection of rules for the placement of a
   9.124 +      child surface relative to a parent surface. Rules can be defined to ensure
   9.125 +      the child surface remains within the visible area's borders, and to
   9.126 +      specify how the child surface changes its position, such as sliding along
   9.127 +      an axis, or flipping around a rectangle. These positioner-created rules are
   9.128 +      constrained by the requirement that a child surface must intersect with or
   9.129 +      be at least partially adjacent to its parent surface.
   9.130 +
   9.131 +      See the various requests for details about possible rules.
   9.132 +
   9.133 +      At the time of the request, the compositor makes a copy of the rules
   9.134 +      specified by the xdg_positioner. Thus, after the request is complete the
   9.135 +      xdg_positioner object can be destroyed or reused; further changes to the
   9.136 +      object will have no effect on previous usages.
   9.137 +
   9.138 +      For an xdg_positioner object to be considered complete, it must have a
   9.139 +      non-zero size set by set_size, and a non-zero anchor rectangle set by
   9.140 +      set_anchor_rect. Passing an incomplete xdg_positioner object when
   9.141 +      positioning a surface raises an error.
   9.142 +    </description>
   9.143 +
   9.144 +    <enum name="error">
   9.145 +      <entry name="invalid_input" value="0" summary="invalid input provided"/>
   9.146 +    </enum>
   9.147 +
   9.148 +    <request name="destroy" type="destructor">
   9.149 +      <description summary="destroy the xdg_positioner object">
   9.150 +	Notify the compositor that the xdg_positioner will no longer be used.
   9.151 +      </description>
   9.152 +    </request>
   9.153 +
   9.154 +    <request name="set_size">
   9.155 +      <description summary="set the size of the to-be positioned rectangle">
   9.156 +	Set the size of the surface that is to be positioned with the positioner
   9.157 +	object. The size is in surface-local coordinates and corresponds to the
   9.158 +	window geometry. See xdg_surface.set_window_geometry.
   9.159 +
   9.160 +	If a zero or negative size is set the invalid_input error is raised.
   9.161 +      </description>
   9.162 +      <arg name="width" type="int" summary="width of positioned rectangle"/>
   9.163 +      <arg name="height" type="int" summary="height of positioned rectangle"/>
   9.164 +    </request>
   9.165 +
   9.166 +    <request name="set_anchor_rect">
   9.167 +      <description summary="set the anchor rectangle within the parent surface">
   9.168 +	Specify the anchor rectangle within the parent surface that the child
   9.169 +	surface will be placed relative to. The rectangle is relative to the
   9.170 +	window geometry as defined by xdg_surface.set_window_geometry of the
   9.171 +	parent surface.
   9.172 +
   9.173 +	When the xdg_positioner object is used to position a child surface, the
   9.174 +	anchor rectangle may not extend outside the window geometry of the
   9.175 +	positioned child's parent surface.
   9.176 +
   9.177 +	If a negative size is set the invalid_input error is raised.
   9.178 +      </description>
   9.179 +      <arg name="x" type="int" summary="x position of anchor rectangle"/>
   9.180 +      <arg name="y" type="int" summary="y position of anchor rectangle"/>
   9.181 +      <arg name="width" type="int" summary="width of anchor rectangle"/>
   9.182 +      <arg name="height" type="int" summary="height of anchor rectangle"/>
   9.183 +    </request>
   9.184 +
   9.185 +    <enum name="anchor">
   9.186 +      <entry name="none" value="0"/>
   9.187 +      <entry name="top" value="1"/>
   9.188 +      <entry name="bottom" value="2"/>
   9.189 +      <entry name="left" value="3"/>
   9.190 +      <entry name="right" value="4"/>
   9.191 +      <entry name="top_left" value="5"/>
   9.192 +      <entry name="bottom_left" value="6"/>
   9.193 +      <entry name="top_right" value="7"/>
   9.194 +      <entry name="bottom_right" value="8"/>
   9.195 +    </enum>
   9.196 +
   9.197 +    <request name="set_anchor">
   9.198 +      <description summary="set anchor rectangle anchor">
   9.199 +	Defines the anchor point for the anchor rectangle. The specified anchor
   9.200 +	is used derive an anchor point that the child surface will be
   9.201 +	positioned relative to. If a corner anchor is set (e.g. 'top_left' or
   9.202 +	'bottom_right'), the anchor point will be at the specified corner;
   9.203 +	otherwise, the derived anchor point will be centered on the specified
   9.204 +	edge, or in the center of the anchor rectangle if no edge is specified.
   9.205 +      </description>
   9.206 +      <arg name="anchor" type="uint" enum="anchor"
   9.207 +	   summary="anchor"/>
   9.208 +    </request>
   9.209 +
   9.210 +    <enum name="gravity">
   9.211 +      <entry name="none" value="0"/>
   9.212 +      <entry name="top" value="1"/>
   9.213 +      <entry name="bottom" value="2"/>
   9.214 +      <entry name="left" value="3"/>
   9.215 +      <entry name="right" value="4"/>
   9.216 +      <entry name="top_left" value="5"/>
   9.217 +      <entry name="bottom_left" value="6"/>
   9.218 +      <entry name="top_right" value="7"/>
   9.219 +      <entry name="bottom_right" value="8"/>
   9.220 +    </enum>
   9.221 +
   9.222 +    <request name="set_gravity">
   9.223 +      <description summary="set child surface gravity">
   9.224 +	Defines in what direction a surface should be positioned, relative to
   9.225 +	the anchor point of the parent surface. If a corner gravity is
   9.226 +	specified (e.g. 'bottom_right' or 'top_left'), then the child surface
   9.227 +	will be placed towards the specified gravity; otherwise, the child
   9.228 +	surface will be centered over the anchor point on any axis that had no
   9.229 +	gravity specified.
   9.230 +      </description>
   9.231 +      <arg name="gravity" type="uint" enum="gravity"
   9.232 +	   summary="gravity direction"/>
   9.233 +    </request>
   9.234 +
   9.235 +    <enum name="constraint_adjustment" bitfield="true">
   9.236 +      <description summary="constraint adjustments">
   9.237 +	The constraint adjustment value define ways the compositor will adjust
   9.238 +	the position of the surface, if the unadjusted position would result
   9.239 +	in the surface being partly constrained.
   9.240 +
   9.241 +	Whether a surface is considered 'constrained' is left to the compositor
   9.242 +	to determine. For example, the surface may be partly outside the
   9.243 +	compositor's defined 'work area', thus necessitating the child surface's
   9.244 +	position be adjusted until it is entirely inside the work area.
   9.245 +
   9.246 +	The adjustments can be combined, according to a defined precedence: 1)
   9.247 +	Flip, 2) Slide, 3) Resize.
   9.248 +      </description>
   9.249 +      <entry name="none" value="0">
   9.250 +	<description summary="don't move the child surface when constrained">
   9.251 +	  Don't alter the surface position even if it is constrained on some
   9.252 +	  axis, for example partially outside the edge of an output.
   9.253 +	</description>
   9.254 +      </entry>
   9.255 +      <entry name="slide_x" value="1">
   9.256 +	<description summary="move along the x axis until unconstrained">
   9.257 +	  Slide the surface along the x axis until it is no longer constrained.
   9.258 +
   9.259 +	  First try to slide towards the direction of the gravity on the x axis
   9.260 +	  until either the edge in the opposite direction of the gravity is
   9.261 +	  unconstrained or the edge in the direction of the gravity is
   9.262 +	  constrained.
   9.263 +
   9.264 +	  Then try to slide towards the opposite direction of the gravity on the
   9.265 +	  x axis until either the edge in the direction of the gravity is
   9.266 +	  unconstrained or the edge in the opposite direction of the gravity is
   9.267 +	  constrained.
   9.268 +	</description>
   9.269 +      </entry>
   9.270 +      <entry name="slide_y" value="2">
   9.271 +	<description summary="move along the y axis until unconstrained">
   9.272 +	  Slide the surface along the y axis until it is no longer constrained.
   9.273 +
   9.274 +	  First try to slide towards the direction of the gravity on the y axis
   9.275 +	  until either the edge in the opposite direction of the gravity is
   9.276 +	  unconstrained or the edge in the direction of the gravity is
   9.277 +	  constrained.
   9.278 +
   9.279 +	  Then try to slide towards the opposite direction of the gravity on the
   9.280 +	  y axis until either the edge in the direction of the gravity is
   9.281 +	  unconstrained or the edge in the opposite direction of the gravity is
   9.282 +	  constrained.
   9.283 +	</description>
   9.284 +      </entry>
   9.285 +      <entry name="flip_x" value="4">
   9.286 +	<description summary="invert the anchor and gravity on the x axis">
   9.287 +	  Invert the anchor and gravity on the x axis if the surface is
   9.288 +	  constrained on the x axis. For example, if the left edge of the
   9.289 +	  surface is constrained, the gravity is 'left' and the anchor is
   9.290 +	  'left', change the gravity to 'right' and the anchor to 'right'.
   9.291 +
   9.292 +	  If the adjusted position also ends up being constrained, the resulting
   9.293 +	  position of the flip_x adjustment will be the one before the
   9.294 +	  adjustment.
   9.295 +	</description>
   9.296 +      </entry>
   9.297 +      <entry name="flip_y" value="8">
   9.298 +	<description summary="invert the anchor and gravity on the y axis">
   9.299 +	  Invert the anchor and gravity on the y axis if the surface is
   9.300 +	  constrained on the y axis. For example, if the bottom edge of the
   9.301 +	  surface is constrained, the gravity is 'bottom' and the anchor is
   9.302 +	  'bottom', change the gravity to 'top' and the anchor to 'top'.
   9.303 +
   9.304 +	  The adjusted position is calculated given the original anchor
   9.305 +	  rectangle and offset, but with the new flipped anchor and gravity
   9.306 +	  values.
   9.307 +
   9.308 +	  If the adjusted position also ends up being constrained, the resulting
   9.309 +	  position of the flip_y adjustment will be the one before the
   9.310 +	  adjustment.
   9.311 +	</description>
   9.312 +      </entry>
   9.313 +      <entry name="resize_x" value="16">
   9.314 +	<description summary="horizontally resize the surface">
   9.315 +	  Resize the surface horizontally so that it is completely
   9.316 +	  unconstrained.
   9.317 +	</description>
   9.318 +      </entry>
   9.319 +      <entry name="resize_y" value="32">
   9.320 +	<description summary="vertically resize the surface">
   9.321 +	  Resize the surface vertically so that it is completely unconstrained.
   9.322 +	</description>
   9.323 +      </entry>
   9.324 +    </enum>
   9.325 +
   9.326 +    <request name="set_constraint_adjustment">
   9.327 +      <description summary="set the adjustment to be done when constrained">
   9.328 +	Specify how the window should be positioned if the originally intended
   9.329 +	position caused the surface to be constrained, meaning at least
   9.330 +	partially outside positioning boundaries set by the compositor. The
   9.331 +	adjustment is set by constructing a bitmask describing the adjustment to
   9.332 +	be made when the surface is constrained on that axis.
   9.333 +
   9.334 +	If no bit for one axis is set, the compositor will assume that the child
   9.335 +	surface should not change its position on that axis when constrained.
   9.336 +
   9.337 +	If more than one bit for one axis is set, the order of how adjustments
   9.338 +	are applied is specified in the corresponding adjustment descriptions.
   9.339 +
   9.340 +	The default adjustment is none.
   9.341 +      </description>
   9.342 +      <arg name="constraint_adjustment" type="uint"
   9.343 +	   summary="bit mask of constraint adjustments"/>
   9.344 +    </request>
   9.345 +
   9.346 +    <request name="set_offset">
   9.347 +      <description summary="set surface position offset">
   9.348 +	Specify the surface position offset relative to the position of the
   9.349 +	anchor on the anchor rectangle and the anchor on the surface. For
   9.350 +	example if the anchor of the anchor rectangle is at (x, y), the surface
   9.351 +	has the gravity bottom|right, and the offset is (ox, oy), the calculated
   9.352 +	surface position will be (x + ox, y + oy). The offset position of the
   9.353 +	surface is the one used for constraint testing. See
   9.354 +	set_constraint_adjustment.
   9.355 +
   9.356 +	An example use case is placing a popup menu on top of a user interface
   9.357 +	element, while aligning the user interface element of the parent surface
   9.358 +	with some user interface element placed somewhere in the popup surface.
   9.359 +      </description>
   9.360 +      <arg name="x" type="int" summary="surface position x offset"/>
   9.361 +      <arg name="y" type="int" summary="surface position y offset"/>
   9.362 +    </request>
   9.363 +  </interface>
   9.364 +
   9.365 +  <interface name="xdg_surface" version="1">
   9.366 +    <description summary="desktop user interface surface base interface">
   9.367 +      An interface that may be implemented by a wl_surface, for
   9.368 +      implementations that provide a desktop-style user interface.
   9.369 +
   9.370 +      It provides a base set of functionality required to construct user
   9.371 +      interface elements requiring management by the compositor, such as
   9.372 +      toplevel windows, menus, etc. The types of functionality are split into
   9.373 +      xdg_surface roles.
   9.374 +
   9.375 +      Creating an xdg_surface does not set the role for a wl_surface. In order
   9.376 +      to map an xdg_surface, the client must create a role-specific object
   9.377 +      using, e.g., get_toplevel, get_popup. The wl_surface for any given
   9.378 +      xdg_surface can have at most one role, and may not be assigned any role
   9.379 +      not based on xdg_surface.
   9.380 +
   9.381 +      A role must be assigned before any other requests are made to the
   9.382 +      xdg_surface object.
   9.383 +
   9.384 +      The client must call wl_surface.commit on the corresponding wl_surface
   9.385 +      for the xdg_surface state to take effect.
   9.386 +
   9.387 +      Creating an xdg_surface from a wl_surface which has a buffer attached or
   9.388 +      committed is a client error, and any attempts by a client to attach or
   9.389 +      manipulate a buffer prior to the first xdg_surface.configure call must
   9.390 +      also be treated as errors.
   9.391 +
   9.392 +      Mapping an xdg_surface-based role surface is defined as making it
   9.393 +      possible for the surface to be shown by the compositor. Note that
   9.394 +      a mapped surface is not guaranteed to be visible once it is mapped.
   9.395 +
   9.396 +      For an xdg_surface to be mapped by the compositor, the following
   9.397 +      conditions must be met:
   9.398 +      (1) the client has assigned an xdg_surface-based role to the surface
   9.399 +      (2) the client has set and committed the xdg_surface state and the
   9.400 +	  role-dependent state to the surface
   9.401 +      (3) the client has committed a buffer to the surface
   9.402 +
   9.403 +      A newly-unmapped surface is considered to have met condition (1) out
   9.404 +      of the 3 required conditions for mapping a surface if its role surface
   9.405 +      has not been destroyed.
   9.406 +    </description>
   9.407 +
   9.408 +    <enum name="error">
   9.409 +      <entry name="not_constructed" value="1"/>
   9.410 +      <entry name="already_constructed" value="2"/>
   9.411 +      <entry name="unconfigured_buffer" value="3"/>
   9.412 +    </enum>
   9.413 +
   9.414 +    <request name="destroy" type="destructor">
   9.415 +      <description summary="destroy the xdg_surface">
   9.416 +	Destroy the xdg_surface object. An xdg_surface must only be destroyed
   9.417 +	after its role object has been destroyed.
   9.418 +      </description>
   9.419 +    </request>
   9.420 +
   9.421 +    <request name="get_toplevel">
   9.422 +      <description summary="assign the xdg_toplevel surface role">
   9.423 +	This creates an xdg_toplevel object for the given xdg_surface and gives
   9.424 +	the associated wl_surface the xdg_toplevel role.
   9.425 +
   9.426 +	See the documentation of xdg_toplevel for more details about what an
   9.427 +	xdg_toplevel is and how it is used.
   9.428 +      </description>
   9.429 +      <arg name="id" type="new_id" interface="xdg_toplevel"/>
   9.430 +    </request>
   9.431 +
   9.432 +    <request name="get_popup">
   9.433 +      <description summary="assign the xdg_popup surface role">
   9.434 +	This creates an xdg_popup object for the given xdg_surface and gives
   9.435 +	the associated wl_surface the xdg_popup role.
   9.436 +
   9.437 +	If null is passed as a parent, a parent surface must be specified using
   9.438 +	some other protocol, before committing the initial state.
   9.439 +
   9.440 +	See the documentation of xdg_popup for more details about what an
   9.441 +	xdg_popup is and how it is used.
   9.442 +      </description>
   9.443 +      <arg name="id" type="new_id" interface="xdg_popup"/>
   9.444 +      <arg name="parent" type="object" interface="xdg_surface" allow-null="true"/>
   9.445 +      <arg name="positioner" type="object" interface="xdg_positioner"/>
   9.446 +    </request>
   9.447 +
   9.448 +    <request name="set_window_geometry">
   9.449 +      <description summary="set the new window geometry">
   9.450 +	The window geometry of a surface is its "visible bounds" from the
   9.451 +	user's perspective. Client-side decorations often have invisible
   9.452 +	portions like drop-shadows which should be ignored for the
   9.453 +	purposes of aligning, placing and constraining windows.
   9.454 +
   9.455 +	The window geometry is double buffered, and will be applied at the
   9.456 +	time wl_surface.commit of the corresponding wl_surface is called.
   9.457 +
   9.458 +	When maintaining a position, the compositor should treat the (x, y)
   9.459 +	coordinate of the window geometry as the top left corner of the window.
   9.460 +	A client changing the (x, y) window geometry coordinate should in
   9.461 +	general not alter the position of the window.
   9.462 +
   9.463 +	Once the window geometry of the surface is set, it is not possible to
   9.464 +	unset it, and it will remain the same until set_window_geometry is
   9.465 +	called again, even if a new subsurface or buffer is attached.
   9.466 +
   9.467 +	If never set, the value is the full bounds of the surface,
   9.468 +	including any subsurfaces. This updates dynamically on every
   9.469 +	commit. This unset is meant for extremely simple clients.
   9.470 +
   9.471 +	The arguments are given in the surface-local coordinate space of
   9.472 +	the wl_surface associated with this xdg_surface.
   9.473 +
   9.474 +	The width and height must be greater than zero. Setting an invalid size
   9.475 +	will raise an error. When applied, the effective window geometry will be
   9.476 +	the set window geometry clamped to the bounding rectangle of the
   9.477 +	combined geometry of the surface of the xdg_surface and the associated
   9.478 +	subsurfaces.
   9.479 +      </description>
   9.480 +      <arg name="x" type="int"/>
   9.481 +      <arg name="y" type="int"/>
   9.482 +      <arg name="width" type="int"/>
   9.483 +      <arg name="height" type="int"/>
   9.484 +    </request>
   9.485 +
   9.486 +    <request name="ack_configure">
   9.487 +      <description summary="ack a configure event">
   9.488 +	When a configure event is received, if a client commits the
   9.489 +	surface in response to the configure event, then the client
   9.490 +	must make an ack_configure request sometime before the commit
   9.491 +	request, passing along the serial of the configure event.
   9.492 +
   9.493 +	For instance, for toplevel surfaces the compositor might use this
   9.494 +	information to move a surface to the top left only when the client has
   9.495 +	drawn itself for the maximized or fullscreen state.
   9.496 +
   9.497 +	If the client receives multiple configure events before it
   9.498 +	can respond to one, it only has to ack the last configure event.
   9.499 +
   9.500 +	A client is not required to commit immediately after sending
   9.501 +	an ack_configure request - it may even ack_configure several times
   9.502 +	before its next surface commit.
   9.503 +
   9.504 +	A client may send multiple ack_configure requests before committing, but
   9.505 +	only the last request sent before a commit indicates which configure
   9.506 +	event the client really is responding to.
   9.507 +      </description>
   9.508 +      <arg name="serial" type="uint" summary="the serial from the configure event"/>
   9.509 +    </request>
   9.510 +
   9.511 +    <event name="configure">
   9.512 +      <description summary="suggest a surface change">
   9.513 +	The configure event marks the end of a configure sequence. A configure
   9.514 +	sequence is a set of one or more events configuring the state of the
   9.515 +	xdg_surface, including the final xdg_surface.configure event.
   9.516 +
   9.517 +	Where applicable, xdg_surface surface roles will during a configure
   9.518 +	sequence extend this event as a latched state sent as events before the
   9.519 +	xdg_surface.configure event. Such events should be considered to make up
   9.520 +	a set of atomically applied configuration states, where the
   9.521 +	xdg_surface.configure commits the accumulated state.
   9.522 +
   9.523 +	Clients should arrange their surface for the new states, and then send
   9.524 +	an ack_configure request with the serial sent in this configure event at
   9.525 +	some point before committing the new surface.
   9.526 +
   9.527 +	If the client receives multiple configure events before it can respond
   9.528 +	to one, it is free to discard all but the last event it received.
   9.529 +      </description>
   9.530 +      <arg name="serial" type="uint" summary="serial of the configure event"/>
   9.531 +    </event>
   9.532 +  </interface>
   9.533 +
   9.534 +  <interface name="xdg_toplevel" version="1">
   9.535 +    <description summary="toplevel surface">
   9.536 +      This interface defines an xdg_surface role which allows a surface to,
   9.537 +      among other things, set window-like properties such as maximize,
   9.538 +      fullscreen, and minimize, set application-specific metadata like title and
   9.539 +      id, and well as trigger user interactive operations such as interactive
   9.540 +      resize and move.
   9.541 +
   9.542 +      Unmapping an xdg_toplevel means that the surface cannot be shown
   9.543 +      by the compositor until it is explicitly mapped again.
   9.544 +      All active operations (e.g., move, resize) are canceled and all
   9.545 +      attributes (e.g. title, state, stacking, ...) are discarded for
   9.546 +      an xdg_toplevel surface when it is unmapped.
   9.547 +
   9.548 +      Attaching a null buffer to a toplevel unmaps the surface.
   9.549 +    </description>
   9.550 +
   9.551 +    <request name="destroy" type="destructor">
   9.552 +      <description summary="destroy the xdg_toplevel">
   9.553 +	This request destroys the role surface and unmaps the surface;
   9.554 +	see "Unmapping" behavior in interface section for details.
   9.555 +      </description>
   9.556 +    </request>
   9.557 +
   9.558 +    <request name="set_parent">
   9.559 +      <description summary="set the parent of this surface">
   9.560 +	Set the "parent" of this surface. This surface should be stacked
   9.561 +	above the parent surface and all other ancestor surfaces.
   9.562 +
   9.563 +	Parent windows should be set on dialogs, toolboxes, or other
   9.564 +	"auxiliary" surfaces, so that the parent is raised when the dialog
   9.565 +	is raised.
   9.566 +
   9.567 +	Setting a null parent for a child window removes any parent-child
   9.568 +	relationship for the child. Setting a null parent for a window which
   9.569 +	currently has no parent is a no-op.
   9.570 +
   9.571 +	If the parent is unmapped then its children are managed as
   9.572 +	though the parent of the now-unmapped parent has become the
   9.573 +	parent of this surface. If no parent exists for the now-unmapped
   9.574 +	parent then the children are managed as though they have no
   9.575 +	parent surface.
   9.576 +      </description>
   9.577 +      <arg name="parent" type="object" interface="xdg_toplevel" allow-null="true"/>
   9.578 +    </request>
   9.579 +
   9.580 +    <request name="set_title">
   9.581 +      <description summary="set surface title">
   9.582 +	Set a short title for the surface.
   9.583 +
   9.584 +	This string may be used to identify the surface in a task bar,
   9.585 +	window list, or other user interface elements provided by the
   9.586 +	compositor.
   9.587 +
   9.588 +	The string must be encoded in UTF-8.
   9.589 +      </description>
   9.590 +      <arg name="title" type="string"/>
   9.591 +    </request>
   9.592 +
   9.593 +    <request name="set_app_id">
   9.594 +      <description summary="set application ID">
   9.595 +	Set an application identifier for the surface.
   9.596 +
   9.597 +	The app ID identifies the general class of applications to which
   9.598 +	the surface belongs. The compositor can use this to group multiple
   9.599 +	surfaces together, or to determine how to launch a new application.
   9.600 +
   9.601 +	For D-Bus activatable applications, the app ID is used as the D-Bus
   9.602 +	service name.
   9.603 +
   9.604 +	The compositor shell will try to group application surfaces together
   9.605 +	by their app ID. As a best practice, it is suggested to select app
   9.606 +	ID's that match the basename of the application's .desktop file.
   9.607 +	For example, "org.freedesktop.FooViewer" where the .desktop file is
   9.608 +	"org.freedesktop.FooViewer.desktop".
   9.609 +
   9.610 +	See the desktop-entry specification [0] for more details on
   9.611 +	application identifiers and how they relate to well-known D-Bus
   9.612 +	names and .desktop files.
   9.613 +
   9.614 +	[0] http://standards.freedesktop.org/desktop-entry-spec/
   9.615 +      </description>
   9.616 +      <arg name="app_id" type="string"/>
   9.617 +    </request>
   9.618 +
   9.619 +    <request name="show_window_menu">
   9.620 +      <description summary="show the window menu">
   9.621 +	Clients implementing client-side decorations might want to show
   9.622 +	a context menu when right-clicking on the decorations, giving the
   9.623 +	user a menu that they can use to maximize or minimize the window.
   9.624 +
   9.625 +	This request asks the compositor to pop up such a window menu at
   9.626 +	the given position, relative to the local surface coordinates of
   9.627 +	the parent surface. There are no guarantees as to what menu items
   9.628 +	the window menu contains.
   9.629 +
   9.630 +	This request must be used in response to some sort of user action
   9.631 +	like a button press, key press, or touch down event.
   9.632 +      </description>
   9.633 +      <arg name="seat" type="object" interface="wl_seat" summary="the wl_seat of the user event"/>
   9.634 +      <arg name="serial" type="uint" summary="the serial of the user event"/>
   9.635 +      <arg name="x" type="int" summary="the x position to pop up the window menu at"/>
   9.636 +      <arg name="y" type="int" summary="the y position to pop up the window menu at"/>
   9.637 +    </request>
   9.638 +
   9.639 +    <request name="move">
   9.640 +      <description summary="start an interactive move">
   9.641 +	Start an interactive, user-driven move of the surface.
   9.642 +
   9.643 +	This request must be used in response to some sort of user action
   9.644 +	like a button press, key press, or touch down event. The passed
   9.645 +	serial is used to determine the type of interactive move (touch,
   9.646 +	pointer, etc).
   9.647 +
   9.648 +	The server may ignore move requests depending on the state of
   9.649 +	the surface (e.g. fullscreen or maximized), or if the passed serial
   9.650 +	is no longer valid.
   9.651 +
   9.652 +	If triggered, the surface will lose the focus of the device
   9.653 +	(wl_pointer, wl_touch, etc) used for the move. It is up to the
   9.654 +	compositor to visually indicate that the move is taking place, such as
   9.655 +	updating a pointer cursor, during the move. There is no guarantee
   9.656 +	that the device focus will return when the move is completed.
   9.657 +      </description>
   9.658 +      <arg name="seat" type="object" interface="wl_seat" summary="the wl_seat of the user event"/>
   9.659 +      <arg name="serial" type="uint" summary="the serial of the user event"/>
   9.660 +    </request>
   9.661 +
   9.662 +    <enum name="resize_edge">
   9.663 +      <description summary="edge values for resizing">
   9.664 +	These values are used to indicate which edge of a surface
   9.665 +	is being dragged in a resize operation.
   9.666 +      </description>
   9.667 +      <entry name="none" value="0"/>
   9.668 +      <entry name="top" value="1"/>
   9.669 +      <entry name="bottom" value="2"/>
   9.670 +      <entry name="left" value="4"/>
   9.671 +      <entry name="top_left" value="5"/>
   9.672 +      <entry name="bottom_left" value="6"/>
   9.673 +      <entry name="right" value="8"/>
   9.674 +      <entry name="top_right" value="9"/>
   9.675 +      <entry name="bottom_right" value="10"/>
   9.676 +    </enum>
   9.677 +
   9.678 +    <request name="resize">
   9.679 +      <description summary="start an interactive resize">
   9.680 +	Start a user-driven, interactive resize of the surface.
   9.681 +
   9.682 +	This request must be used in response to some sort of user action
   9.683 +	like a button press, key press, or touch down event. The passed
   9.684 +	serial is used to determine the type of interactive resize (touch,
   9.685 +	pointer, etc).
   9.686 +
   9.687 +	The server may ignore resize requests depending on the state of
   9.688 +	the surface (e.g. fullscreen or maximized).
   9.689 +
   9.690 +	If triggered, the client will receive configure events with the
   9.691 +	"resize" state enum value and the expected sizes. See the "resize"
   9.692 +	enum value for more details about what is required. The client
   9.693 +	must also acknowledge configure events using "ack_configure". After
   9.694 +	the resize is completed, the client will receive another "configure"
   9.695 +	event without the resize state.
   9.696 +
   9.697 +	If triggered, the surface also will lose the focus of the device
   9.698 +	(wl_pointer, wl_touch, etc) used for the resize. It is up to the
   9.699 +	compositor to visually indicate that the resize is taking place,
   9.700 +	such as updating a pointer cursor, during the resize. There is no
   9.701 +	guarantee that the device focus will return when the resize is
   9.702 +	completed.
   9.703 +
   9.704 +	The edges parameter specifies how the surface should be resized,
   9.705 +	and is one of the values of the resize_edge enum. The compositor
   9.706 +	may use this information to update the surface position for
   9.707 +	example when dragging the top left corner. The compositor may also
   9.708 +	use this information to adapt its behavior, e.g. choose an
   9.709 +	appropriate cursor image.
   9.710 +      </description>
   9.711 +      <arg name="seat" type="object" interface="wl_seat" summary="the wl_seat of the user event"/>
   9.712 +      <arg name="serial" type="uint" summary="the serial of the user event"/>
   9.713 +      <arg name="edges" type="uint" summary="which edge or corner is being dragged"/>
   9.714 +    </request>
   9.715 +
   9.716 +    <enum name="state">
   9.717 +      <description summary="types of state on the surface">
   9.718 +	The different state values used on the surface. This is designed for
   9.719 +	state values like maximized, fullscreen. It is paired with the
   9.720 +	configure event to ensure that both the client and the compositor
   9.721 +	setting the state can be synchronized.
   9.722 +
   9.723 +	States set in this way are double-buffered. They will get applied on
   9.724 +	the next commit.
   9.725 +      </description>
   9.726 +      <entry name="maximized" value="1" summary="the surface is maximized">
   9.727 +	<description summary="the surface is maximized">
   9.728 +	  The surface is maximized. The window geometry specified in the configure
   9.729 +	  event must be obeyed by the client.
   9.730 +	</description>
   9.731 +      </entry>
   9.732 +      <entry name="fullscreen" value="2" summary="the surface is fullscreen">
   9.733 +	<description summary="the surface is fullscreen">
   9.734 +	  The surface is fullscreen. The window geometry specified in the
   9.735 +	  configure event is a maximum; the client cannot resize beyond it. For
   9.736 +	  a surface to cover the whole fullscreened area, the geometry
   9.737 +	  dimensions must be obeyed by the client. For more details, see
   9.738 +	  xdg_toplevel.set_fullscreen.
   9.739 +	</description>
   9.740 +      </entry>
   9.741 +      <entry name="resizing" value="3" summary="the surface is being resized">
   9.742 +	<description summary="the surface is being resized">
   9.743 +	  The surface is being resized. The window geometry specified in the
   9.744 +	  configure event is a maximum; the client cannot resize beyond it.
   9.745 +	  Clients that have aspect ratio or cell sizing configuration can use
   9.746 +	  a smaller size, however.
   9.747 +	</description>
   9.748 +      </entry>
   9.749 +      <entry name="activated" value="4" summary="the surface is now activated">
   9.750 +	<description summary="the surface is now activated">
   9.751 +	  Client window decorations should be painted as if the window is
   9.752 +	  active. Do not assume this means that the window actually has
   9.753 +	  keyboard or pointer focus.
   9.754 +	</description>
   9.755 +      </entry>
   9.756 +    </enum>
   9.757 +
   9.758 +    <request name="set_max_size">
   9.759 +      <description summary="set the maximum size">
   9.760 +	Set a maximum size for the window.
   9.761 +
   9.762 +	The client can specify a maximum size so that the compositor does
   9.763 +	not try to configure the window beyond this size.
   9.764 +
   9.765 +	The width and height arguments are in window geometry coordinates.
   9.766 +	See xdg_surface.set_window_geometry.
   9.767 +
   9.768 +	Values set in this way are double-buffered. They will get applied
   9.769 +	on the next commit.
   9.770 +
   9.771 +	The compositor can use this information to allow or disallow
   9.772 +	different states like maximize or fullscreen and draw accurate
   9.773 +	animations.
   9.774 +
   9.775 +	Similarly, a tiling window manager may use this information to
   9.776 +	place and resize client windows in a more effective way.
   9.777 +
   9.778 +	The client should not rely on the compositor to obey the maximum
   9.779 +	size. The compositor may decide to ignore the values set by the
   9.780 +	client and request a larger size.
   9.781 +
   9.782 +	If never set, or a value of zero in the request, means that the
   9.783 +	client has no expected maximum size in the given dimension.
   9.784 +	As a result, a client wishing to reset the maximum size
   9.785 +	to an unspecified state can use zero for width and height in the
   9.786 +	request.
   9.787 +
   9.788 +	Requesting a maximum size to be smaller than the minimum size of
   9.789 +	a surface is illegal and will result in a protocol error.
   9.790 +
   9.791 +	The width and height must be greater than or equal to zero. Using
   9.792 +	strictly negative values for width and height will result in a
   9.793 +	protocol error.
   9.794 +      </description>
   9.795 +      <arg name="width" type="int"/>
   9.796 +      <arg name="height" type="int"/>
   9.797 +    </request>
   9.798 +
   9.799 +    <request name="set_min_size">
   9.800 +      <description summary="set the minimum size">
   9.801 +	Set a minimum size for the window.
   9.802 +
   9.803 +	The client can specify a minimum size so that the compositor does
   9.804 +	not try to configure the window below this size.
   9.805 +
   9.806 +	The width and height arguments are in window geometry coordinates.
   9.807 +	See xdg_surface.set_window_geometry.
   9.808 +
   9.809 +	Values set in this way are double-buffered. They will get applied
   9.810 +	on the next commit.
   9.811 +
   9.812 +	The compositor can use this information to allow or disallow
   9.813 +	different states like maximize or fullscreen and draw accurate
   9.814 +	animations.
   9.815 +
   9.816 +	Similarly, a tiling window manager may use this information to
   9.817 +	place and resize client windows in a more effective way.
   9.818 +
   9.819 +	The client should not rely on the compositor to obey the minimum
   9.820 +	size. The compositor may decide to ignore the values set by the
   9.821 +	client and request a smaller size.
   9.822 +
   9.823 +	If never set, or a value of zero in the request, means that the
   9.824 +	client has no expected minimum size in the given dimension.
   9.825 +	As a result, a client wishing to reset the minimum size
   9.826 +	to an unspecified state can use zero for width and height in the
   9.827 +	request.
   9.828 +
   9.829 +	Requesting a minimum size to be larger than the maximum size of
   9.830 +	a surface is illegal and will result in a protocol error.
   9.831 +
   9.832 +	The width and height must be greater than or equal to zero. Using
   9.833 +	strictly negative values for width and height will result in a
   9.834 +	protocol error.
   9.835 +      </description>
   9.836 +      <arg name="width" type="int"/>
   9.837 +      <arg name="height" type="int"/>
   9.838 +    </request>
   9.839 +
   9.840 +    <request name="set_maximized">
   9.841 +      <description summary="maximize the window">
   9.842 +	Maximize the surface.
   9.843 +
   9.844 +	After requesting that the surface should be maximized, the compositor
   9.845 +	will respond by emitting a configure event with the "maximized" state
   9.846 +	and the required window geometry. The client should then update its
   9.847 +	content, drawing it in a maximized state, i.e. without shadow or other
   9.848 +	decoration outside of the window geometry. The client must also
   9.849 +	acknowledge the configure when committing the new content (see
   9.850 +	ack_configure).
   9.851 +
   9.852 +	It is up to the compositor to decide how and where to maximize the
   9.853 +	surface, for example which output and what region of the screen should
   9.854 +	be used.
   9.855 +
   9.856 +	If the surface was already maximized, the compositor will still emit
   9.857 +	a configure event with the "maximized" state.
   9.858 +
   9.859 +	If the surface is in a fullscreen state, this request has no direct
   9.860 +	effect. It will alter the state the surface is returned to when
   9.861 +	unmaximized if not overridden by the compositor.
   9.862 +      </description>
   9.863 +    </request>
   9.864 +
   9.865 +    <request name="unset_maximized">
   9.866 +      <description summary="unmaximize the window">
   9.867 +	Unmaximize the surface.
   9.868 +
   9.869 +	After requesting that the surface should be unmaximized, the compositor
   9.870 +	will respond by emitting a configure event without the "maximized"
   9.871 +	state. If available, the compositor will include the window geometry
   9.872 +	dimensions the window had prior to being maximized in the configure
   9.873 +	event. The client must then update its content, drawing it in a
   9.874 +	regular state, i.e. potentially with shadow, etc. The client must also
   9.875 +	acknowledge the configure when committing the new content (see
   9.876 +	ack_configure).
   9.877 +
   9.878 +	It is up to the compositor to position the surface after it was
   9.879 +	unmaximized; usually the position the surface had before maximizing, if
   9.880 +	applicable.
   9.881 +
   9.882 +	If the surface was already not maximized, the compositor will still
   9.883 +	emit a configure event without the "maximized" state.
   9.884 +
   9.885 +	If the surface is in a fullscreen state, this request has no direct
   9.886 +	effect. It will alter the state the surface is returned to when
   9.887 +	unmaximized if not overridden by the compositor.
   9.888 +      </description>
   9.889 +    </request>
   9.890 +
   9.891 +    <request name="set_fullscreen">
   9.892 +      <description summary="set the window as fullscreen on an output">
   9.893 +	Make the surface fullscreen.
   9.894 +
   9.895 +	After requesting that the surface should be fullscreened, the
   9.896 +	compositor will respond by emitting a configure event with the
   9.897 +	"fullscreen" state and the fullscreen window geometry. The client must
   9.898 +	also acknowledge the configure when committing the new content (see
   9.899 +	ack_configure).
   9.900 +
   9.901 +	The output passed by the request indicates the client's preference as
   9.902 +	to which display it should be set fullscreen on. If this value is NULL,
   9.903 +	it's up to the compositor to choose which display will be used to map
   9.904 +	this surface.
   9.905 +
   9.906 +	If the surface doesn't cover the whole output, the compositor will
   9.907 +	position the surface in the center of the output and compensate with
   9.908 +	with border fill covering the rest of the output. The content of the
   9.909 +	border fill is undefined, but should be assumed to be in some way that
   9.910 +	attempts to blend into the surrounding area (e.g. solid black).
   9.911 +
   9.912 +	If the fullscreened surface is not opaque, the compositor must make
   9.913 +	sure that other screen content not part of the same surface tree (made
   9.914 +	up of subsurfaces, popups or similarly coupled surfaces) are not
   9.915 +	visible below the fullscreened surface.
   9.916 +      </description>
   9.917 +      <arg name="output" type="object" interface="wl_output" allow-null="true"/>
   9.918 +    </request>
   9.919 +
   9.920 +    <request name="unset_fullscreen">
   9.921 +      <description summary="unset the window as fullscreen">
   9.922 +	Make the surface no longer fullscreen.
   9.923 +
   9.924 +	After requesting that the surface should be unfullscreened, the
   9.925 +	compositor will respond by emitting a configure event without the
   9.926 +	"fullscreen" state.
   9.927 +
   9.928 +	Making a surface unfullscreen sets states for the surface based on the following:
   9.929 +	* the state(s) it may have had before becoming fullscreen
   9.930 +	* any state(s) decided by the compositor
   9.931 +	* any state(s) requested by the client while the surface was fullscreen
   9.932 +
   9.933 +	The compositor may include the previous window geometry dimensions in
   9.934 +	the configure event, if applicable.
   9.935 +
   9.936 +	The client must also acknowledge the configure when committing the new
   9.937 +	content (see ack_configure).
   9.938 +      </description>
   9.939 +    </request>
   9.940 +
   9.941 +    <request name="set_minimized">
   9.942 +      <description summary="set the window as minimized">
   9.943 +	Request that the compositor minimize your surface. There is no
   9.944 +	way to know if the surface is currently minimized, nor is there
   9.945 +	any way to unset minimization on this surface.
   9.946 +
   9.947 +	If you are looking to throttle redrawing when minimized, please
   9.948 +	instead use the wl_surface.frame event for this, as this will
   9.949 +	also work with live previews on windows in Alt-Tab, Expose or
   9.950 +	similar compositor features.
   9.951 +      </description>
   9.952 +    </request>
   9.953 +
   9.954 +    <event name="configure">
   9.955 +      <description summary="suggest a surface change">
   9.956 +	This configure event asks the client to resize its toplevel surface or
   9.957 +	to change its state. The configured state should not be applied
   9.958 +	immediately. See xdg_surface.configure for details.
   9.959 +
   9.960 +	The width and height arguments specify a hint to the window
   9.961 +	about how its surface should be resized in window geometry
   9.962 +	coordinates. See set_window_geometry.
   9.963 +
   9.964 +	If the width or height arguments are zero, it means the client
   9.965 +	should decide its own window dimension. This may happen when the
   9.966 +	compositor needs to configure the state of the surface but doesn't
   9.967 +	have any information about any previous or expected dimension.
   9.968 +
   9.969 +	The states listed in the event specify how the width/height
   9.970 +	arguments should be interpreted, and possibly how it should be
   9.971 +	drawn.
   9.972 +
   9.973 +	Clients must send an ack_configure in response to this event. See
   9.974 +	xdg_surface.configure and xdg_surface.ack_configure for details.
   9.975 +      </description>
   9.976 +      <arg name="width" type="int"/>
   9.977 +      <arg name="height" type="int"/>
   9.978 +      <arg name="states" type="array"/>
   9.979 +    </event>
   9.980 +
   9.981 +    <event name="close">
   9.982 +      <description summary="surface wants to be closed">
   9.983 +	The close event is sent by the compositor when the user
   9.984 +	wants the surface to be closed. This should be equivalent to
   9.985 +	the user clicking the close button in client-side decorations,
   9.986 +	if your application has any.
   9.987 +
   9.988 +	This is only a request that the user intends to close the
   9.989 +	window. The client may choose to ignore this request, or show
   9.990 +	a dialog to ask the user to save their data, etc.
   9.991 +      </description>
   9.992 +    </event>
   9.993 +  </interface>
   9.994 +
   9.995 +  <interface name="xdg_popup" version="1">
   9.996 +    <description summary="short-lived, popup surfaces for menus">
   9.997 +      A popup surface is a short-lived, temporary surface. It can be used to
   9.998 +      implement for example menus, popovers, tooltips and other similar user
   9.999 +      interface concepts.
  9.1000 +
  9.1001 +      A popup can be made to take an explicit grab. See xdg_popup.grab for
  9.1002 +      details.
  9.1003 +
  9.1004 +      When the popup is dismissed, a popup_done event will be sent out, and at
  9.1005 +      the same time the surface will be unmapped. See the xdg_popup.popup_done
  9.1006 +      event for details.
  9.1007 +
  9.1008 +      Explicitly destroying the xdg_popup object will also dismiss the popup and
  9.1009 +      unmap the surface. Clients that want to dismiss the popup when another
  9.1010 +      surface of their own is clicked should dismiss the popup using the destroy
  9.1011 +      request.
  9.1012 +
  9.1013 +      The parent surface must have either the xdg_toplevel or xdg_popup surface
  9.1014 +      role.
  9.1015 +
  9.1016 +      A newly created xdg_popup will be stacked on top of all previously created
  9.1017 +      xdg_popup surfaces associated with the same xdg_toplevel.
  9.1018 +
  9.1019 +      The parent of an xdg_popup must be mapped (see the xdg_surface
  9.1020 +      description) before the xdg_popup itself.
  9.1021 +
  9.1022 +      The x and y arguments passed when creating the popup object specify
  9.1023 +      where the top left of the popup should be placed, relative to the
  9.1024 +      local surface coordinates of the parent surface. See
  9.1025 +      xdg_surface.get_popup. An xdg_popup must intersect with or be at least
  9.1026 +      partially adjacent to its parent surface.
  9.1027 +
  9.1028 +      The client must call wl_surface.commit on the corresponding wl_surface
  9.1029 +      for the xdg_popup state to take effect.
  9.1030 +    </description>
  9.1031 +
  9.1032 +    <enum name="error">
  9.1033 +      <entry name="invalid_grab" value="0"
  9.1034 +	     summary="tried to grab after being mapped"/>
  9.1035 +    </enum>
  9.1036 +
  9.1037 +    <request name="destroy" type="destructor">
  9.1038 +      <description summary="remove xdg_popup interface">
  9.1039 +	This destroys the popup. Explicitly destroying the xdg_popup
  9.1040 +	object will also dismiss the popup, and unmap the surface.
  9.1041 +
  9.1042 +	If this xdg_popup is not the "topmost" popup, a protocol error
  9.1043 +	will be sent.
  9.1044 +      </description>
  9.1045 +    </request>
  9.1046 +
  9.1047 +    <request name="grab">
  9.1048 +      <description summary="make the popup take an explicit grab">
  9.1049 +	This request makes the created popup take an explicit grab. An explicit
  9.1050 +	grab will be dismissed when the user dismisses the popup, or when the
  9.1051 +	client destroys the xdg_popup. This can be done by the user clicking
  9.1052 +	outside the surface, using the keyboard, or even locking the screen
  9.1053 +	through closing the lid or a timeout.
  9.1054 +
  9.1055 +	If the compositor denies the grab, the popup will be immediately
  9.1056 +	dismissed.
  9.1057 +
  9.1058 +	This request must be used in response to some sort of user action like a
  9.1059 +	button press, key press, or touch down event. The serial number of the
  9.1060 +	event should be passed as 'serial'.
  9.1061 +
  9.1062 +	The parent of a grabbing popup must either be an xdg_toplevel surface or
  9.1063 +	another xdg_popup with an explicit grab. If the parent is another
  9.1064 +	xdg_popup it means that the popups are nested, with this popup now being
  9.1065 +	the topmost popup.
  9.1066 +
  9.1067 +	Nested popups must be destroyed in the reverse order they were created
  9.1068 +	in, e.g. the only popup you are allowed to destroy at all times is the
  9.1069 +	topmost one.
  9.1070 +
  9.1071 +	When compositors choose to dismiss a popup, they may dismiss every
  9.1072 +	nested grabbing popup as well. When a compositor dismisses popups, it
  9.1073 +	will follow the same dismissing order as required from the client.
  9.1074 +
  9.1075 +	The parent of a grabbing popup must either be another xdg_popup with an
  9.1076 +	active explicit grab, or an xdg_popup or xdg_toplevel, if there are no
  9.1077 +	explicit grabs already taken.
  9.1078 +
  9.1079 +	If the topmost grabbing popup is destroyed, the grab will be returned to
  9.1080 +	the parent of the popup, if that parent previously had an explicit grab.
  9.1081 +
  9.1082 +	If the parent is a grabbing popup which has already been dismissed, this
  9.1083 +	popup will be immediately dismissed. If the parent is a popup that did
  9.1084 +	not take an explicit grab, an error will be raised.
  9.1085 +
  9.1086 +	During a popup grab, the client owning the grab will receive pointer
  9.1087 +	and touch events for all their surfaces as normal (similar to an
  9.1088 +	"owner-events" grab in X11 parlance), while the top most grabbing popup
  9.1089 +	will always have keyboard focus.
  9.1090 +      </description>
  9.1091 +      <arg name="seat" type="object" interface="wl_seat"
  9.1092 +	   summary="the wl_seat of the user event"/>
  9.1093 +      <arg name="serial" type="uint" summary="the serial of the user event"/>
  9.1094 +    </request>
  9.1095 +
  9.1096 +    <event name="configure">
  9.1097 +      <description summary="configure the popup surface">
  9.1098 +	This event asks the popup surface to configure itself given the
  9.1099 +	configuration. The configured state should not be applied immediately.
  9.1100 +	See xdg_surface.configure for details.
  9.1101 +
  9.1102 +	The x and y arguments represent the position the popup was placed at
  9.1103 +	given the xdg_positioner rule, relative to the upper left corner of the
  9.1104 +	window geometry of the parent surface.
  9.1105 +      </description>
  9.1106 +      <arg name="x" type="int"
  9.1107 +	   summary="x position relative to parent surface window geometry"/>
  9.1108 +      <arg name="y" type="int"
  9.1109 +	   summary="y position relative to parent surface window geometry"/>
  9.1110 +      <arg name="width" type="int" summary="window geometry width"/>
  9.1111 +      <arg name="height" type="int" summary="window geometry height"/>
  9.1112 +    </event>
  9.1113 +
  9.1114 +    <event name="popup_done">
  9.1115 +      <description summary="popup interaction is done">
  9.1116 +	The popup_done event is sent out when a popup is dismissed by the
  9.1117 +	compositor. The client should destroy the xdg_popup object at this
  9.1118 +	point.
  9.1119 +      </description>
  9.1120 +    </event>
  9.1121 +
  9.1122 +  </interface>
  9.1123 +</protocol>