<div dir="ltr">This doesn't work in the case of tiling WMs which may want some up-front information about window sizes so they can lay them out correctly. Currently, we say that the maximize and fullscreen states are strictly sized, and clients *must* submit window geometry that's equivalent to that, so there needs to be some negotiation from the point of the client so it can say that it won't render a buffer at a silly size.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 5, 2014 at 9:11 PM, Bill Spitzak <span dir="ltr"><<a href="mailto:spitzak@gmail.com" target="_blank">spitzak@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This should not be necessary. Client can just ignore the requested size and make the buffer the size it wants.<div class="HOEnZb">
<div class="h5"><br>
<br>
On 08/05/2014 12:07 PM, Jari Vetoniemi wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Rationale for this patch is to provide way for applications that can't go below/above<br>
certain bounds to inform compositor about it.<br>
<br>
More feedback is needed. For example are maximimum size useful for any<br>
particular application?<br>
---<br>
protocol/xdg-shell.xml | 18 ++++++++++++++++++<br>
1 file changed, 18 insertions(+)<br>
<br>
diff --git a/protocol/xdg-shell.xml b/protocol/xdg-shell.xml<br>
index bd36231..6e48ae6 100644<br>
--- a/protocol/xdg-shell.xml<br>
+++ b/protocol/xdg-shell.xml<br>
@@ -235,6 +235,24 @@<br>
<arg name="edges" type="uint" summary="which edge or corner is being dragged"/><br>
</request><br>
<br>
+ <request name="set_size_hints"><br>
+ <description summary="provide surface size hints"><br>
+ Server should use these hints to figure out how much surface may be,<br>
+ resized so that the content still remains sane. Hints will remain<br>
+ the same until set_size_hints is requested again.<br>
+<br>
+ Hints set this way are double buffered. They will get applied on<br>
+ the next commit.<br>
+<br>
+ These hints should take effect regardless of the surface state.<br>
+ A size less than zero unsets the hint.<br>
+ </description><br>
+ <arg name="min_width" type="int" summary="minimum width of the surface"/><br>
+ <arg name="min_height" type="int" summary="minimum height of the surface"/><br>
+ <arg name="max_width" type="int" summary="maximum width of the surface"/><br>
+ <arg name="max_height" type="int" summary="maximum height of the surface"/><br>
+ </request><br>
+<br>
<enum name="state"><br>
<description summary="types of state on the surface"><br>
The different state values used on the surface. This is designed for<br>
<br>
</blockquote></div></div><div class="HOEnZb"><div class="h5">
______________________________<u></u>_________________<br>
wayland-devel mailing list<br>
<a href="mailto:wayland-devel@lists.freedesktop.org" target="_blank">wayland-devel@lists.<u></u>freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/wayland-devel" target="_blank">http://lists.freedesktop.org/<u></u>mailman/listinfo/wayland-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br> Jasper<br>
</div>