Module layout_backend 

The layout engines a binary carries, how a launch installs one, and the system set that marks where layout is solved.

Each engine registers a LayoutBackend into the app’s LayoutBackends from its own crate, and the launch installs the highest-priority one with install_layout. The core and the runtime name no engine.

Structs

LayoutBackend

One layout engine: its name, its rank, and how to make it.

LayoutSolve

The systems in crate::tick::TickStage::LayoutSync that write each entity’s crate::components::Transform for this tick.

Functions

install_layout

Install the highest-priority layout engine registered into app, and return its name. An error says the build carries none.

Type Aliases

LayoutBackends

Main-world registry of the layout engines this binary carries. An engine’s capability install adds itself with crate::backends::register_backend.