[PATCH 2/2] shell: account for the subsurfaces when going fullscreen or maximizing

[Pekka Paalanen]

On Tue, 26 Feb 2013 09:22:44 -0800
Bill Spitzak <spitzak at gmail.com> wrote:

> On 02/25/2013 09:59 AM, Giulio Camuffo wrote:
> > We must calculate the bounding box of the surface + subsurfaces set and use
> > that when maximizing the window or going fullscreen.
> 
> I think it would be much better for the client to just be able to say 
> "pretend this shell surface is this big, even though the buffer attached 
> to it is a different rectangle". In this case whatever the parent 
> surface is would claim it occupied an area that included the edge 
> decoration subsurfaces.
> 
> This will also allow subsurfaces to extend outside what the user thinks 
> of as the window area. Also it seems vastly simpler, I'm pretty certain 
> the client will know this information easily.

Do I understand correctly, that you would like to add protocol, so
that clients could provide information, that the server can
easily compute from the information it already has?

Sorry, I don't think so. There needs to be some other reason to add
more protocol.

> If there is api added so the client knows what portion of the surface is 
> actually visible and not clipped by output edges or panels, it can use 
> this to avoid allocating buffer for and drawing invisible portions, 
> which I think will be a big win by making maximize a lot simpler.

I have no idea what you are trying to say here. Do you want to
change how maximize works? So that clients would always render full
decorations, the compositor would clip some decorations away
because the window is maximized, and then you want the client to
query the compositor about which areas it is clipping away, so that
the client would not need to draw them?

I hope I just didn't understand.


- pq