| |||||||||||||
Wayland and Weston 1.0 releasedWayland and Weston 1.0 releasedPosted Oct 26, 2012 16:30 UTC (Fri) by renox (subscriber, #23785)In reply to: Wayland and Weston 1.0 released by raven667 Parent article: Wayland and Weston 1.0 released
>> So it's either that, or you can leave the window contents in place at the last size the client gave you, and track the new size with an outline. Which is 100% possible to implement within Wayland.
> This also seems to cover the use case you are looking for, similar to how some older WMs worked.
Not really, you loose information about how your window will look when resized which is annoying, but I think that this configuration is the best when you're using remote applications on high latency communications, so it's still an interesting configuration.
(Log in to post comments)
Wayland and Weston 1.0 released Posted Oct 26, 2012 16:32 UTC (Fri) by daniels (subscriber, #16193) [Link]
> Not really, you loose information about how your window will look when resized
Which you also lose whilst scaling.
Wayland and Weston 1.0 released Posted Oct 26, 2012 18:02 UTC (Fri) by renox (subscriber, #23785) [Link]
>> Not really, you loose information about how your window will look when resized
>Which you also lose whilst scaling.
Which are very temporary, short situations.
Wayland and Weston 1.0 released Posted Oct 26, 2012 18:37 UTC (Fri) by daniels (subscriber, #16193) [Link]
> Which are very temporary, short situations.
Equally as temporary and short as for client-side decorations. Although I still maintain CSDs are likely to be even more responsive for the reasons I listed above.
|
|||||||||||||