Struct WindowConfig 

pub struct WindowConfig {
    pub title: String,
    pub width: u32,
    pub height: u32,
    pub target_fps: Option<u32>,
    pub fill_viewport: bool,
}

Window configuration for run_windowed / run_app.

Deliberately renderer-agnostic: pixel dimensions, not grid/font/scale. Use fit to derive the pixel size from a presenter’s own cell geometry.

Fields

title: String

Window title.

width: u32

Initial inner width in physical pixels.

height: u32

Initial inner height in physical pixels.

target_fps: Option<u32>

Optional frame-rate cap. None = uncapped (native) / display refresh (wasm, which is always rAF-driven).

fill_viewport: bool

On wasm32, size (and keep resizing) the canvas to fill the browser viewport instead of width/height – a full-screen, mobile-web-app feel for games that want it. Has no effect on native, where the OS window is already sized to width/height and the window manager owns further resizing either way.

Defaults to false in fit: most demos/examples should render at their natural grid size (cols x cell_w by rows x cell_h) wherever they land on the page, not stretch to fill whatever viewport happens to be hosting them. Opt in explicitly for an app-like, full-screen game.

Implementations

impl WindowConfig

pub fn fit<P: Presenter>( presenter: &P, title: impl Into<String>, target_fps: Option<u32>, ) -> Self

Size the window to exactly fit presenter’s grid: cols x cell_w by rows x cell_h physical pixels.

This is why renderer crates don’t need their own windowing code: the grid/cell geometry already lives behind Presenter::size and Presenter::cell_size.