Skip to main content

Module startup

Module startup 

Source
Expand description

The generic boot-completion signal (design.md §9.1) (DB.5).

Published once per boot, after Editor::boot returns, by each renderer’s post-boot seam (TUI App::new, GPUI GpuiApp::new) — carrying the file (if any) passed on the command line. Declared here, alongside the existing crate::ModeEvent typed-event precedent, rather than as a per-renderer ad hoc signal, so any subsystem’s install(&mut boot) can subscribe via the generic typed-event bus without a lattice-host dependency. lattice-dashboard’s startup-trigger subscription is the first consumer (lattice_dashboard::install).

Structs§

Startup
Fired once per boot after Editor::boot returns. opened_file is the path (if any) the renderer’s post-boot seam captured from the boot Document before it moved into Editor::boot (which consumes it).