Repository navigation
[Linux] Implement Window::SetMinimumSize / SetMaximumSize #55
Description
Activity
Fixed in 10ac6fe (Linux) and 4ef0521 (Windows + tests).
- Linux: min/max sizes are applied as GTK geometry hints and combined with
SetAspectRatio, so setting one no longer clears the other. The public frame size is converted to the GDK surface (CSD shadows, server-side frames). Hints are refreshed after mapping and layout changes, deferred until GTK finishes its resize. - Windows (found while testing):
WM_GETMINMAXINFOread the limits from theWindowRegistrywrapper, which may not be the instance that set them, so they could be silently ignored. The handler now reads the setter's state, and width and height can be bounded independently.
Verified with the new desktop tests (no synthetic input):
window_size_constraints_linux_teston GNOME Wayland (36 checks), Xwayland (48), Xvfb/Openbox and Weston;window_size_constraints_windows_teston Windows (7). Also checked by hand withwindow_example(min 400×300, max 1000×700) on macOS, Windows and Linux.- Linux: min/max sizes are applied as GTK geometry hints and combined with
- added 2 commits that reference this issue
on Sep 22, 2026
Window::SetMinimumSize()andWindow::SetMaximumSize()are stubs on Linux (src/platform/linux/window_linux.cpp), so min/max size constraints set through nativeapi have no effect there. The getters return whatever was stored.Expected: enforce the constraints with
gtk_window_set_geometry_hints()(GDK_HINT_MIN_SIZE/GDK_HINT_MAX_SIZE), combined with the aspect-ratio hints thatSetAspectRatio()already sets. Otherwise one call would overwrite the other's hints. Check that:Background, from window_manager (which is moving onto nativeapi in 0.6.0):
gtk_window_set_geometry_hints