User: Password:
|
|
Subscribe / Log in / New account

The Wayland Situation: Facts About X vs. Wayland (Phoronix)

The Wayland Situation: Facts About X vs. Wayland (Phoronix)

Posted Jun 14, 2013 14:25 UTC (Fri) by michaeljt (subscriber, #39183)
In reply to: The Wayland Situation: Facts About X vs. Wayland (Phoronix) by renox
Parent article: The Wayland Situation: Facts About X vs. Wayland (Phoronix)

>>When I last delved into this it was up to the clients to move their own windows

>No, I made a similar mistake but this is wrong..
>What happen is: when you click on the tittle-bar, the client recognize that you want to move its window and it asks the compositor to put the window in a "move mode": then when you move your mouse the compositor will move your window without the client being involved.

I seem to recall hearing something about the client informing the window manager in advance about which areas of the window could be used for dragging, so that it would work even if the client was not responsive. I might be wrong though.

>IMHO this isn't very good here, like you, if a client is slow/busy I prefer that resizing its window has smooth resizing of the outline even if the content can become "ugly" (when the client fails to provide the content in time) to 'perfect frame' but with jerky/lagging.

I have to say that I actually prefer resizing to be the client's business, having seen enough cases of the window manager and client mis-co-ordinating that. In extreme cases the window manager could still clip the client.


(Log in to post comments)


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds