summaryrefslogtreecommitdiff
path: root/protocol/wayland.xml
diff options
context:
space:
mode:
authorKristian Høgsberg <krh@bitplanet.net>2011-01-28 15:18:33 -0500
committerKristian Høgsberg <krh@bitplanet.net>2011-01-28 15:18:33 -0500
commit0ce245761c85e989f08e4136bd91b149156e82e0 (patch)
tree95cdf35228275c023917f19137afa8e772743559 /protocol/wayland.xml
parent5e4d83f499c218d09917f90dddb2d9348552c4b3 (diff)
Add initial basic support for fullscreen surfaces
Diffstat (limited to 'protocol/wayland.xml')
-rw-r--r--protocol/wayland.xml10
1 files changed, 10 insertions, 0 deletions
diff --git a/protocol/wayland.xml b/protocol/wayland.xml
index 13c71bd..a9f96b6 100644
--- a/protocol/wayland.xml
+++ b/protocol/wayland.xml
@@ -368,6 +368,16 @@
<arg name="flags" type="uint"/>
</request>
+ <!-- Map the surface as a fullscreen surface. There are a number
+ of options here: on which output? if the surface size doesn't
+ match the output size, do we scale, change resolution, or add
+ black borders? is that something the client controls? what
+ about transient surfaces, do they float on top of the
+ fullscreen? what if there's already a fullscreen surface on
+ the output, maybe you can only go fullscreen if you're
+ active? -->
+ <request name="map_fullscreen"/>
+
<!-- Notify the server that the attached buffer's contents have
changed, and request a redraw. The arguments allow you to
damage only a part of the surface, but the server may ignore