Modules

Module pages document widget namespaces like iced::widget::button, including family-specific style and helper APIs.

# Use this when...

• You need deeper APIs than the free constructor call.
• You want to discover module-level style/state types.
• You are building reusable abstractions around one widget family.

# Minimal example

use iced::widget::button;

let save = button("Save").on_press(Message::Save);

# How it works

In practice, you often start from constructors and then come back to module pages for advanced options (theme/style catalogs, helper types, and integration points).

# Common patterns

use iced::widget::{button, container, text_input};

let form = container(
    iced::widget::column![
        text_input("Name", &state.name).on_input(Message::NameChanged),
        button("Submit").on_press(Message::Submit),
    ]
);

# Gotchas / tips

• Constructor and module names can differ slightly (combo_box, text_input, etc.).
• If a constructor page seems sparse, check its module page for richer context.
• Keep imports explicit while learning; it clarifies which API surface you are using.

# Module Index

• Button
• Checkbox
• Combo Box
• Container
• Float
• Grid
• Keyed
• Operation
• Overlay
• Pane Grid
• Pick List
• Progress Bar
• Radio
• Row
• Rule
• Scrollable
• Sensor
• Shader
• Slider
• Space
• Table
• Text
• Text Editor
• Text Input
• Theme
• Toggler
• Tooltip
• Vertical Slider

# Related

• Families
• Constructors