forked from AuroraMiddleware/gtk
3b91c20eac
We're normally going from a fixed size to a floating state when we're using the saved size, meaning we're practically always going towards a state where the shadow margin will non-empty. However, if we don't include any margin when creating a new configure request, we'll end up resizing to a slightly smaller size as gtk will cut off the margin from the configure request when changing the window widget size. This wasn't visible when e.g. going from maximized to floating, as we'd add the shadow margin at a later point, which would effectively "grow" the widnow size, but when we're going from tiled to floating, we both start and end with a non-empty shadow margin, meaning we'd shrink ever so slightly every time going between tiled and floating. |
||
|---|---|---|
| .. | ||
| protocol | ||
| gdkapplaunchcontext-wayland.c | ||
| gdkcursor-wayland.c | ||
| gdkdevice-wayland.c | ||
| gdkdisplay-wayland.c | ||
| gdkdisplay-wayland.h | ||
| gdkdnd-wayland.c | ||
| gdkeventsource.c | ||
| gdkglcontext-wayland.c | ||
| gdkglcontext-wayland.h | ||
| gdkkeys-wayland.c | ||
| gdkmonitor-wayland.c | ||
| gdkmonitor-wayland.h | ||
| gdkprivate-wayland.h | ||
| gdkscreen-wayland.c | ||
| gdkseat-wayland.h | ||
| gdkselection-wayland.c | ||
| gdkwayland.h | ||
| gdkwaylanddevice.h | ||
| gdkwaylanddisplay.h | ||
| gdkwaylandglcontext.h | ||
| gdkwaylandmonitor.h | ||
| gdkwaylandselection.h | ||
| gdkwaylandwindow.h | ||
| gdkwindow-wayland.c | ||
| Makefile.am | ||
| meson.build | ||
| wm-button-layout-translation.c | ||
| wm-button-layout-translation.h | ||