Module - Text Input

Authoritative source: ref/doc/iced/widget/text_input/index.html.

# Rustdoc description

Text inputs display fields that can be filled with text.

# When to use

Use this module when you need the widget family and related style/state APIs grouped under iced::widget::text_input.

# Example References

• ref/examples/changelog/src/main.rs
• ref/examples/integration/src/controls.rs
• ref/examples/lazy/src/main.rs
• ref/examples/modal/src/main.rs
• ref/examples/multi_window/src/main.rs
• ref/examples/qr_code/src/main.rs

# Inline Examples (from rustdoc)

use iced::widget::text_input;

struct State {
   content: String,
}

#[derive(Debug, Clone)]
enum Message {
    ContentChanged(String)
}

fn view(state: &State) -> Element<'_, Message> {
    text_input("Type something here...", &state.content)
        .on_input(Message::ContentChanged)
        .into()
}

fn update(state: &mut State, message: Message) {
    match message {
        Message::ContentChanged(content) => {
            state.content = content;
        }
    }
}

# Related

• Modules
• Constructors

# Use this when...

• You need module-level APIs beyond the basic constructor call.
• You want family-specific style/state traits and helper types.
• You are building reusable widget abstractions.

# Minimal example

// Start with the constructor from this module family in `view`.
// Then move to module APIs for deeper customization.

# How it works

Module docs explain the namespace that groups constructors, types, and related traits. In everyday app code, this helps you discover advanced options after basic usage works.

# Common patterns

// Message flow pattern:
// widget interaction -> Message -> update -> state change -> rerender

# Gotchas / tips

• Check this page together with its family page for complete context.
• Verify trait bounds and associated types in rustdoc when custom styling fails.
• Keep module imports explicit while learning.