Hey,<div><br></div><div>Sorry to bring up this dead thread, but I was just curious to know if any of the suggestions about fullscreen mode and non-native resolutions have been implemented, or are still planned in Wayland?</div>
<div><br></div><div>Luke.<br><br><div class="gmail_quote">2010/11/10 Luke Benstead <span dir="ltr"><<a href="mailto:kazade@gmail.com">kazade@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br><br><div class="gmail_quote"><div class="im">2010/11/10 Kristian Høgsberg <span dir="ltr"><<a href="mailto:krh@bitplanet.net" target="_blank">krh@bitplanet.net</a>></span> <br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Either way, a native resolution fullscreen mode is definitely planned.<br>
Both scaling (with or without aspect ratio/black bars) and native<br>
modes (we can page flip directly to the applications buffer) make<br>
sense, but I think that will be policy/configuration options in the<br>
compositor. What will be in the protocol will be a way to request to<br>
be fullscreen, which the compositor will honor when the application<br>
has focus, but it will always be possible to alt-tab away (or press<br>
the "home button" or similar). So the compositor is in control, it<br>
will change the resolution, scale and draw black bars, or maybe even<br>
just center the application window and fade out the rest of the<br>
desktop around it.<br>
<br></blockquote></div><div><br>Excellent! I can't wait for that!<br> </div><div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
This also ties in with capturing the mouse pointer and relative events<br>
(which Carsten also talks about in his mail). Typically games also<br>
want to make sure the pointer stays inside the window and they want<br>
relative events. It's no good if you're trying to turn around in<br>
quake and the pointer leaves the window or hits the screen edge. X<br>
applications solve this by grabbing the mouse, confining it to the<br>
window and continuously warping the cursor into the center to simulate<br>
relative events. This is obviously a hack, and wayland isn't going to<br>
support open-ended pointer or keyboard grabs, nor warping the pointer.<br>
Instead, we provide relative events when the device generates them,<br>
and in fullscreen mode, all the events go to the fullscreen<br>
application, so no need to confine the pointer. <br></blockquote></div><div><br>Brilliant, the Wine project will love you guys - they've had a nightmare with the lack of relative mouse info from X (until recently) - that is of course if/when they write a Wayland driver.<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Anyway, this is all kinda half-baked, but it is the general direction<br>
I see this going.<br>
<font color="#888888"><br>
Kristian<br></font></blockquote></div><div><br>Thanks Kristian! <br></div></div><br>
</blockquote></div><br></div>