[weston PATCH v6 1/2] add implementation for set_maximised

[Juan Zhao]

  On 02/07/2012 05:08 AM, Bill Spitzak wrote:
>
>> The output choosing code in the server would likely take the surface
>> bounding box, and find the output where most of the surface is. This is
>> how it already works, when we choose which output to synchronise the
>> surface to.
>
> Yes this is exactly what I want to enforce, by making sure the client 
> cannot send any information other than "this is the box it would be in 
> if not maximized, and I want it maximized". The client is not allowed 
> to choose the output except by giving the unmaximized location, so 
> there cannot be conflicting information when the compositor wants to 
> maximize a window. 
In current solution we discussed, the client can only set to be 
maximised in the output it was bound to. I think this can resolve your 
main concern, about choosing another output it is not on when maximised.

The unmaximized location is determined by "set_toplevel" now. Maybe we 
can adds some parameter in "set_toplevel" to define the top-left coordinate?