love.window.setMode with resizable flag lacks minimum size constraints

Answer

love.window.setMode does not enforce a minimum size when the resizable flag is true; the underlying SDL2 layer allows the window to be shrunk to 1×1 pixels.

Confirmed facts

• love.window.setMode only sets the initial size; subsequent user resizing is handled by SDL2 without Love2D interference.
• Love2D provides no API to query or set minimum/maximum window dimensions.
• The love.resize(w, h) callback receives the new size after the user drags the window border.

Likely explanation

The function forwards the request to SDL2, which honors the resizable flag but offers no way to attach size constraints; consequently Love2D cannot automatically clamp the dimensions.

Steps to enforce a minimum size

1. In love.load set the initial window with the desired resizable flag:

function love.load()
    love.window.setMode(800, 600, {resizable=true, vsync=true})
end

2. Implement love.resize to clamp the width and height to your minima and, only if the clamped values differ from the received ones, call love.window.setMode again:

local MIN_W, MIN_H = 400, 300
function love.resize(w, h)
    local changed = false
    if w < MIN_W then w = MIN_W; changed = true end
    if h < MIN_H then h = MIN_H; changed = true end
    if changed then
        love.window.setMode(w, h, {resizable=true})
    end
    -- use w and h for rendering or store them
end

3. Optionally store the clamped dimensions in globals or use love.window.getWidth() and love.window.getHeight() after the potential second setMode call.

Verification

• Run the game, try to resize the window below MIN_W or MIN_H; the window should snap back to the clamped size.
• Print love.window.getWidth() and love.window.getHeight() inside love.resize before and after the conditional setMode to confirm the values.
• Test on both Windows and Linux (SDL2 backend) to ensure consistent behavior.

Impact on existing projects

Adding optional minWidth and minHeight parameters to love.window.setMode would be backward‑compatible; projects that do not supply them would retain the current unrestricted resizing behavior. Only projects that rely on the ability to shrink the window to arbitrary sizes would need to adjust their expectations or explicitly disable the new limits.