TimePicker
Family: Inputs & Forms
Namespace: Tessera.Controls
Use TimePicker when this interaction is the best match for your screen workflow.
When to use
- You need a
TimePicker-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 TimePicker
{
Title = "TimePicker"
};
return Screen.Build(window => window.Body(body => body.Center(widget, width: 44, height: 9)));Common pitfalls
- Do not choose
TimePickerby 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 |
|---|---|
ActiveField | TimeField |
ActiveFieldStyle | TesseraStyle |
Border | BorderStyle |
BorderStyleText | TesseraStyle |
DisabledValueStyle | TesseraStyle |
FocusedBorderStyleText | TesseraStyle |
FocusedTitleStyle | TesseraStyle |
FocusMarker | string |
HourStep | int |
HoveredFieldStyle | TesseraStyle |
IsDisabled | bool |
IsFocused | bool |
IsReadOnly | bool |
LastCommittedTime | TimeOnly? |
MinuteStep | int |
Padding | Thickness |
SecondStep | int |
SeparatorStyle | TesseraStyle |
ShowFocusMarker | bool |
Title | string |
TitleStyle | TesseraStyle |
Value | TimeOnly |
ValueTextStyle | TesseraStyle |
Public events
| Event | Type |
|---|---|
ValueChanged | EventHandler<TimeValueChangedEventArgs>? |