Constructor - Container

Authoritative source: ref/doc/iced/widget/fn.container.html.

# Rustdoc summary

Creates a new Container with the provided content.

# Verified signature

pub fn container<'a, Message, Theme, Renderer>(
    content: impl Into<Element<'a, Message, Theme, Renderer>>,
) -> Container<'a, Message, Theme, Renderer>
where
    Theme: Catalog + 'a,
    Renderer: Renderer,

# When to use

Use this constructor/helper as the typed entrypoint for the widget or layout helper it creates.

# Why to use

It gives explicit widget construction with compile-time type checking and builder chaining.

# Example References

• ref/examples/clock/src/main.rs
• ref/examples/layout/src/main.rs
• ref/examples/delineate/src/main.rs
• ref/examples/ferris/src/main.rs
• ref/examples/game_of_life/src/main.rs
• ref/examples/modal/src/main.rs

# Inline Examples (from rustdoc)

use iced::widget::container;

enum Message {
    // ...
}

fn view(state: &State) -> Element<'_, Message> {
    container("This text is centered inside a rounded box!")
        .padding(10)
        .center(800)
        .style(container::rounded_box)
        .into()
}

# Related

• Constructors
• Elements

# Use this when...

• You want the canonical entrypoint for creating this widget/helper.
• You need concrete constructor arguments and builder chaining.
• You are wiring UI interactions into typed messages.

# Minimal example

// Call this constructor in `view`, then map events to Message variants.

# How it works

Constructors return typed widget values. You configure behavior via builder methods and emit Message values for update to handle.

# Common patterns

// Keep constructor calls close to their message mapping.
// Prefer small helper functions for repeated widget setups.

# Gotchas / tips

• Re-check argument order in the verified signature on this page.
• Keep side effects out of view; trigger them from update with Task.
• Use the related family page when deciding between module/element APIs.