Stepper

Family: Inputs & Forms
Namespace: Tessera.Controls

Use Stepper when this interaction is the best match for your screen workflow.

When to use

• You need a Stepper-style interaction inside the inputs & forms lane.
• A titled widget surface improves scanability in dense shells.
• You want explicit user-driven events routed into app state updates.

Minimal usage

csharp.cs

using Tessera.Controls;
using Tessera.Layout;

var widget = new Stepper
{
    Title = "Stepper"
};

return Screen.Build(window => window.Body(body => body.Center(widget, width: 44, height: 9)));

Common pitfalls

• Do not choose Stepper by name only; validate it against the target workflow.
• Keep this control scoped to the inputs & forms concern; avoid cross-layer state coupling.
• Handle control events by posting/processing messages; avoid hidden mutation in render paths.
• Set focused/normal styles intentionally so keyboard focus remains obvious.
• Keep disabled state explicit and reversible so users understand why actions are blocked.

Public properties

Property	Type
ActiveStepStyle	TesseraStyle
CompletedStepStyle	TesseraStyle
Connector	string
ConnectorStyle	TesseraStyle
DisabledStepStyle	TesseraStyle
FocusedTitleStyle	TesseraStyle
FocusMarker	string
IsDisabled	bool
IsFocused	bool
IsReadOnly	bool
PendingStepStyle	TesseraStyle
ShowFocusMarker	bool
StepTextStyle	TesseraStyle
Title	string
TitleStyle	TesseraStyle

Public events

Event	Type
CurrentStepChanged	EventHandler<StepperCurrentStepChangedEventArgs>?
SelectionChanged	EventHandler<StepperCurrentStepChangedEventArgs>?

Related docs

• Widget Reference
• Widgets Overview
• Public API Inventory