VirtualizedListView<T>
Family: Navigation & Workflow
Namespace: Tessera.Controls
Use VirtualizedListView<T> when this interaction is the best match for your screen workflow.
When to use
- You need a
VirtualizedListView-style interaction inside the navigation & workflow 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 VirtualizedListView<T>
{
Title = "VirtualizedListView"
};
return Screen.Build(window => window.Body(body => body.Center(widget, width: 44, height: 9)));Common pitfalls
- Do not choose
VirtualizedListViewby name only; validate it against the target workflow. - Keep this control scoped to the navigation & workflow 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 |
|---|---|
Border | BorderStyle |
BorderStyleText | TesseraStyle |
Count | int |
DefaultRowStyle | TesseraStyle |
DisabledRowStyle | TesseraStyle |
EmptyText | string |
FocusedBorderStyleText | TesseraStyle |
FocusedTitleStyle | TesseraStyle |
FocusMarker | string |
HoveredRowStyle | TesseraStyle |
IsDisabled | bool |
IsFocused | bool |
IsReadOnly | bool |
Options | VirtualizedListViewOptions |
Padding | Thickness |
SelectedIndex | int |
SelectedRowStyle | TesseraStyle |
ShowFocusMarker | bool |
Title | string |
TitleStyle | TesseraStyle |
Public events
| Event | Type |
|---|---|
SelectionChanged | EventHandler<ListSelectionChangedEventArgs<T>>? |