Function settings 

pub fn settings<V: IntoView>(content: impl Fn() -> V) -> SceneHandle

Settings { content } — the window behind ⌘, on macOS.

Examples found in repository

examples/scenes.rs (line 294)

fn main() {
    // `--describe` asks the same question the event loop would and prints the
    // answer: what Swift types came out of this. Useful because the types are
    // the claim — `_TupleScene<(WindowGroup<AnyView>, Settings<AnyView>, …)>` is
    // what Swift builds from four scenes in a row, and nothing about a window
    // appearing would say whether that is what got built.
    #[cfg(target_os = "macos")]
    if std::env::args().any(|a| a == "--describe") {
        let whole = body();
        println!("App.Body\n  {}", whole.type_name());
        for (name, s) in [
            ("window_group", scene::window_group(main_window)),
            ("settings", scene::settings(settings_pane)),
            ("window", scene::window("Utility", "utility", utility_window)),
            ("menu_bar_extra", scene::menu_bar_extra("Count", "star.fill", menu_bar_item)),
        ] {
            println!("{name}\n  {}", s.type_name());
        }
        // Built through the macro, so this also checks that what `scenes!`
        // expands to is the same thing the free functions build.
        let one = scenes! { window_group { text("x") } commands { menu("M") { text("x") } } };
        println!("scenes! with one menu\n  {}", one.type_name());
        return;
    }

    // `--probe` launches for real and reports what AppKit built, then quits.
    #[cfg(target_os = "macos")]
    if std::env::args().any(|a| a == "--probe") {
        probe::schedule(2.5);
    }

    app::run_scene(body)
}