mirror of
https://github.com/brl/mutter.git
synced 2024-11-24 17:10:40 -05:00
2919a7f25f
In the old, synchronous X.org world, we could assume that a state change always meant a synchronizing the window geometry right after. After firing an operation that would change the window state, such as maximizing or tiling the window, With Wayland, however, this is not valid anymore, since Wayland is asynchronous. In this scenario, we call meta_window_move_resize_internal() twice: when the user executes an state-changing operation, and when the server ACKs this operation. This breaks the previous assumptions, and as a consequence, it breaks the GNOME Shell animations in Wayland. The solution is giving the MetaWindow control over the time when the window geometry is synchronized with the compositor. That is done by introducing a new result flag. Wayland asks for a compositor sync after receiving an ACK from the server, while X11 asks for it right away. Fixes #78 |
||
|---|---|---|
| .. | ||
| atomnames.h | ||
| events.c | ||
| events.h | ||
| group-private.h | ||
| group-props.c | ||
| group-props.h | ||
| group.c | ||
| iconcache.c | ||
| iconcache.h | ||
| mutter-Xatomtype.h | ||
| session.c | ||
| session.h | ||
| window-props.c | ||
| window-props.h | ||
| window-x11-private.h | ||
| window-x11.c | ||
| window-x11.h | ||
| xprops.c | ||
| xprops.h | ||