slint-ui

Route the call through Bridge::run or Bridge::run_with_error, which spawns a plain thread for the Launcher call and posts the result back with upgrade_in_event_loop. Never invoke a Launcher method directly inside a callback body.

Declare a per-screen global like InstancesState in ui/state.slint; the screen binds its layout to the global and Rust accesses it via window.global::<XState>(). Initialize every property empty and set all of them in the screen's open function.

A ComboBox reports every arrow step and wheel tick as selected, not just the settled value. Hold the pending value in a property and restart a named debounce Timer (about 500 ms) so the save fires once after the user stops.

No. ModelRc and slint::Image are UI-thread only and must be constructed inside the upgrade_in_event_loop closure or on the UI thread. Build raw data on the worker, then convert it after posting back.

Build the real AppWindow over a Launcher on a temp root, then address elements by their snake_case ids like "InstancesScreen::create_button" using click, type_into, and wait_until. Element names are only emitted in debug builds.

A dialog kept mounted retains a full-window TouchArea holding the pointer grab. Mount every dialog inside an `if <State>.xxx_open:` block so a closed dialog has no element in the tree, and gate touch areas on enabled: root.open.