[PATCH] Introduce set_size_hints xdg_surface request.

Jasper St. Pierre jstpierre at mecheye.net
Wed Aug 6 18:34:28 PDT 2014


On Wed, Aug 6, 2014 at 9:30 PM, Bill Spitzak <spitzak at gmail.com> wrote:

> On 08/06/2014 05:38 PM, Jasper St. Pierre wrote:
>
>  For the maximized or fullscreen states, the client must always submit
>> window geometry that is the configured size. No exceptions.
>>
>
> Are you sure? I know the fullscreen supports scaling or centering of a
> smaller surface (though the client has to set the resize type first). What
> happens if the size is wrong? Is the client killed with a protocol error?
>

The scaling system was removed in xdg-shell. If we want to add it back, we
should probably look more closely at the zoom and crop extension for
scaling surfaces. It is not a protocol error to submit incorrect window
geometry right now, but we might want to make it one eventually. The case
of "undefined" or "invalid" values in protocols needs more semantics, and
I'm going to talk more about this tomorrow in my reply to Pekka.


> It is true that fullscreen and maximized are in fact "tiled" window
> managers. Any ideas for these and for tiled window managers apply to each
> other and the api should be the same.
>

We are working things on one step at a time. Jari was working on a tiling
WM using the maximized state. We will introduce new states as the needs
arise. Currently, hacking something up with maximized was enough to get a
prototype out, but there was certainly talk about doing more here.

-- 
  Jasper
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20140806/d74a7b92/attachment.html>


More information about the wayland-devel mailing list