Family - Progress Bar

This page unifies related iced::widget APIs for the Progress Bar family.

# API surfaces

• Module: iced::widget::progress_bar
• Constructor: iced::widget::progress_bar
• Element: iced::widget::ProgressBar

# Surface summaries

# Module

Progress bars visualize the progression of an extended computer operation, such as a download, file transfer, or installation.

# Constructor

Creates a new ProgressBar .

# Element

A bar that displays progress.

# Verified constructor signature

pub fn progress_bar<'a, Theme>(
    range: RangeInclusive<f32>,
    value: f32,
) -> ProgressBar<'a, Theme>
where
    Theme: Catalog + 'a,

# Verified element declaration

pub struct ProgressBar<'a, Theme = Theme>
where
    Theme: Catalog,{ /* private fields */ }

# Example References

• ref/examples/progress_bar/src/main.rs
• ref/examples/changelog/src/main.rs
• ref/examples/styling/src/main.rs
• ref/examples/scrollable/src/main.rs
• ref/examples/download_progress/src/main.rs

# Inline Examples (from rustdoc)

# Constructor example

use iced::widget::progress_bar;

struct State {
   progress: f32,
}

enum Message {
    // ...
}

fn view(state: &State) -> Element<'_, Message> {
    progress_bar(0.0..=100.0, state.progress).into()
}

# Element example

use iced::widget::progress_bar;

struct State {
   progress: f32,
}

enum Message {
    // ...
}

fn view(state: &State) -> Element<'_, Message> {
    progress_bar(0.0..=100.0, state.progress).into()
}

# Related

• Families
• Modules
• Constructors
• Elements

# Use this when...

• You want one page that links module, constructor, and element surfaces.
• You are deciding which API surface to start from.
• You need a practical map for this widget domain.

# Minimal example

// Typical flow:
// 1) Start with constructor usage.
// 2) Move to module docs for style/state details.
// 3) Use element docs for type-level control.

# How it works

Family pages connect related docs so you do not miss capabilities that are split across constructor/module/element pages.

# Common patterns

// Build with constructor APIs first,
// then refine behavior/styles through related module and element docs.

# Gotchas / tips

• Family routes normalize naming; module/function/struct names may differ slightly.
• Prefer this page as your entrypoint when learning unfamiliar widgets.
• Follow example references here before inventing integration patterns.