Struct GraphicsSystem 

pub struct GraphicsSystem { /* private fields */ }

Drives the render backend: builds it at init, submits a frame per step.

Implementations

impl GraphicsSystem

pub fn new() -> Self

Fresh renderer driver with no backend yet. Config (frames-in-flight, clear color, max_frames, shadow-map size) is read from the world’s GraphicsConfig in System::init.

impl GraphicsSystem

pub fn hot_reload_apply_parts<'a>( &'a mut self, backend: &'a mut dyn RenderBackend, ) -> HotReloadApplyParts<'a>

Disjoint mutable screen of the backend + hot-reload bookkeeping the binary-only DebugHook::tick reload drive applies changes through. The caller supplies the backend (borrowed from the world’s parked slot via World::systems_and_render_backend) since this system yields it after init. The library never calls this (the asset hot-reload drive lives in the cn debug binary), so it reads as dead code under cargo check --lib.

pub fn take_hot_reload_sources(&mut self) -> Option<HotReloadSources>

Take the init-captured hot-reload source catalogues, leaving None behind. The cn debug drive calls this once on its first tick to build the filesystem watcher + AssetHotReloadState. None under cn run, or when no file-backed asset / world.jsonl was declared.

Trait Implementations

impl Debug for GraphicsSystem

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for GraphicsSystem

fn default() -> Self

Returns the “default value” for a type.

impl System for GraphicsSystem

fn init(&mut self, ctx: &mut PipelineContext<'_>)

Run once at World::start, before the first step.

fn step(&mut self, ctx: &mut PipelineContext<'_>) -> StepResult

Run once per tick.

fn access(&self) -> Access

The data step may touch, consulted once when the schedule is built (after init, so a data-dependent system can compute it from its compiled state). The default claims everything: an undeclared system is ordered against all others and never runs concurrently, which is always safe. Declaring narrower access is what admits a system to shared waves and to debug-build access validation.