iced

Iced Docs

Source-verified docs generated from /src/content.

Reference

Element - Row

Struct reference for iced::widget::Row.

Version: latest | Last updated: 2026-02-19

Element - Row

Authoritative source: ref/doc/iced/widget/struct.Row.html.

# Rustdoc summary

Creates a Stack with the given children.

# Verified type declaration

rust
pub struct Row<'a, Message, Theme = Theme, Renderer = Renderer<Renderer, Renderer>> { /* private fields */ }

# When to use

Use this element struct when you need direct type-level control over a widget value.

# Why to use

It enables strongly typed composition and explicit builder method flows.

# Example References

  • ref/examples/game_of_life/src/preset.rs
  • ref/examples/layout/src/main.rs
  • ref/examples/tour/src/main.rs
  • ref/examples/changelog/src/main.rs
  • ref/examples/styling/src/main.rs

# Inline Examples (from rustdoc)

rust
use iced::widget::{button, row};

#[derive(Debug, Clone)]
enum Message {
    // ...
}

fn view(state: &State) -> Element<'_, Message> {
    row![
        "I am to the left!",
        button("I am in the middle!"),
        "I am to the right!",
    ].into()
}

# Use this when...

  • You need the concrete widget struct type in signatures.
  • You are debugging type errors involving generic bounds.
  • You want lower-level control than constructor-only docs provide.

# Minimal example

rust
// Constructors usually produce this element type.
// Name the type explicitly only when type-level APIs need it.

# How it works

Element structs are the underlying widget types used by constructors. Most app code can stay constructor-first, then use element docs for advanced typing/customization.

# Common patterns

rust
// Use constructors in normal UI code,
// and reserve explicit element types for reusable abstractions.

# Gotchas / tips

  • You usually do not need to construct element structs directly.
  • Read trait bounds carefully when adding custom renderer/theme types.
  • If a method is missing, check the related module page.