Controls
Drawn controls for the parts of a window that are not a grid: buttons, text fields, tabs, option groups, combo boxes, number and date fields, menus, toolbars, images, panels and a free drawing surface — styled by the same sheets as the board, focusable, and announced to screen readers.
Preview Part of ArionUI Core (ArionUI.Presentation.Controls). Enough for business forms, not every control a desktop toolkit has; the API may still change between preview versions. What was built most recently is listed at the end.
Built today
| Control | What it is |
|---|---|
Button | Text and Click; Space and Enter press it. The theme draws it quiet; the classes primary and neutral give the other two looks, or Visual sets one in code. |
TextBox | One line: caret, selection by mouse and keyboard, a word or everything by double and triple click, clipboard, undo and redo inside the field, an edit menu on right-click. Changed, Committed (Enter), Cancelled (Escape); a placeholder through Field.Placeholder. |
TextArea | Several lines that wrap at the field's width and scroll inside the field; only the lines in view are drawn. Text, Changed, Placeholder, VisibleLines, ReadOnly. |
TabControl | Pages behind a strip of tabs (TabPage, TabItem); SelectedIndex, closable tabs with Closing to refuse, Ctrl+Tab between pages. |
RadioGroup, RadioButton | One choice out of several: Selected and Select by index, vertical or Horizontal; arrow keys move the choice. |
ComboBox | A value picked from Items with type-ahead, or with IsEditable free text with suggestions; Value, ValueChanged, Placeholder. |
NumericUpDown | A number with Minimum, Maximum, Step, LargeStep, a Format, an optional input Mask and the culture's separators; arrows, Page Up/Down and the mouse wheel step it. |
DatePicker | A date typed through a mask in the culture's format, or picked from a calendar pane; Minimum, Maximum, AllowsEmpty. |
MenuBar, ToolBar | A window's menu bar with F10 and Alt+letter access keys (MenuBarItem), and a row of commands with separators. |
ArionImage | A picture from an ArionBitmap (PNG, JPEG, BMP and what else the decoder reads), Stretch, AltText. |
CheckBox, ToggleSwitch | Text, Value and Toggle; Space toggles. The switch's knob is animated. |
ArionSlider | Minimum, Maximum, Step, LargeStep, Value, Changed, and a Format for what a screen reader hears. |
DropDownButton | The closed state of a drop-down. Open receives the button's rectangle and opens whatever the application wants there — a menu, a list. |
Label | Text from a Func<string>, with MaxLines for wrapping and a Style of its own, or the font of the tile around it. |
Drawing | A free drawing surface: Paint gets the render surface and the rectangle. |
Separator, Spacer, MenuRow | A hairline, an empty stretch, and a focusable row with your own drawing that activates on click or Enter. |
StackPanel | Children vertical or horizontal (Horizontal), each Auto, Fill or a fixed size along the main axis, with Gap and MainPadding. |
ScrollPanel | One child, scrolled vertically with drawn scroll bars; BringIntoView, ScrollTo. |
Card | A frame with fill, border, radius, padding and shadow around one child. |
Board, ViewTile, ElementTile | The grid of tracks, any view as a tile, and a single cell element — sparkline, donut, bullet, progress — as a tile. See Board. |
A small form
Controls read the application's state through Func<> and write it through Action: there is no binding layer between them and your objects. A control asks for its text when it draws, so it always shows the current value.
using ArionUI.Presentation.Controls; // TextBox, CheckBox, ToggleSwitch, ArionSlider, Button
var name = new TextBox { Id = "name", Spoken = () => "Name", Committed = () => Log("name entered") };
var weekly = new CheckBox
{
Id = "weekly",
Text = () => "Send me the weekly report",
Value = () => settings.Weekly,
Toggle = () => settings.Weekly = !settings.Weekly,
};
var alerts = new ToggleSwitch
{
Text = () => "Alerts",
Value = () => settings.Alerts,
Toggle = () => settings.Alerts = !settings.Alerts,
};
var volume = new ArionSlider
{
Minimum = 0,
Maximum = 100,
Step = 5,
Value = () => settings.Volume,
Changed = v => settings.Volume = v,
Format = v => $"{v:0} %",
};
var save = new Button
{
Id = "save",
Text = () => "Save",
Classes = ["primary"], // the theme's primary look
EnabledWhen = () => name.Text.Length > 0,
Click = Save,
};Laid out with a stack, inside a scrolling card:
var form = new StackPanel { Gap = 10 }
.Add(new Label { Text = () => "Newsletter" })
.Add(name)
.Add(weekly)
.Add(new Separator())
.Add(new StackPanel { Horizontal = true, Gap = 12 }
.Add(new Spacer(), StackPanel.Fill) // pushes the button right
.Add(save, cross: 30));
var panel = new Card(new ScrollPanel(form)) { Padding = 16, CornerRadius = 10 };On a board, a form is usually a nested board instead — labels in an auto column, fields in a star column — as on Board.
Tabs
A TabControl holds pages; each page is any control — a stack, a nested board. The strip is one tab stop, Tab goes from it into the page, and the pages not shown are no tab stops and no screen-reader parts.
var tabs = new TabControl { Id = "customer", AccessibleName = () => "Customer" }
.Add(() => "General", new StackPanel { Gap = 8 }
.Add(new Label { Text = () => "Name" })
.Add(new TextBox { Id = "name", Spoken = () => "Name" })
.Add(new CheckBox { Text = () => "Regular customer", Value = () => order.Regular, Toggle = () => order.Regular = !order.Regular }))
.Add(() => "Address", new StackPanel { Gap = 8 }
.Add(new Label { Text = () => "Street" })
.Add(new TextBox { Id = "street", Spoken = () => "Street" }))
.Add(() => "Notes", new Label { Text = () => "No notes yet." }, canClose: true);
tabs.SelectedIndex = 1; // Ctrl+Tab and Ctrl+Shift+Tab switch pages tooAdd and remove pages of a shown board inside Board.Mutate. The tabs take their look from Select.Type<TabItem>(), the selected one in the Checked state.
Option groups and combo boxes
var delivery = new RadioGroup
{
Id = "delivery",
AccessibleName = () => "Delivery",
Selected = () => order.Delivery,
Select = i => order.Delivery = i,
}
.Add("Standard (3-5 days)")
.Add("Express (next day)")
.Add("Pick up in store");A combo box holds its value itself. Closed it shows the value; open, the grid's own combo list hangs below it in the pane stack, above the whole board. Down and Up pick without opening, typing jumps to the value it begins; an editable box filters its suggestions as you type.
var country = new ComboBox
{
Id = "country",
Items = ["Austria", "Germany", "Italy", "Switzerland"],
Spoken = () => "Country",
ValueChanged = v => order.Country = v,
};
country.Value = order.Country;
var city = new ComboBox
{
Id = "city",
IsEditable = true, // free text, with suggestions from Items
Items = ["Graz", "Linz", "Salzburg", "Vienna"],
Placeholder = "Type a city",
Spoken = () => "City",
};ValueChanged runs where the value changed — a pick from the open list comes outside the board's change tracking, so a handler that changes other tiles does it inside Board.Mutate. Bound to a view model, the board does that for you (Board).
Text, numbers and dates
var notes = new TextArea
{
Id = "notes",
Spoken = () => "Notes",
Placeholder = "Notes for the order",
VisibleLines = 6,
Changed = () => Log("notes changed"),
};
notes.Text = "Deliver to the back entrance.";Number and date fields read and write through delegates, like a check box. They format and parse with the culture (Culture, else the current one): a German machine types 12,50 and 24.12.2026, an American one 12.50 and 12/24/2026.
var quantity = new NumericUpDown
{
Id = "quantity",
Value = () => order.Quantity,
Changed = v => order.Quantity = v,
Maximum = 999,
Spoken = () => "Quantity",
Tooltip = () => "0 to 999 pieces",
};
var price = new NumericUpDown
{
Id = "price",
Value = () => order.Price,
Changed = v => order.Price = v,
Maximum = 10_000,
Step = 0.5,
Format = "N2",
Spoken = () => "Unit price",
};
var due = new DatePicker
{
Id = "due",
Value = () => order.Due,
Changed = d => order.Due = d,
Minimum = new DateTime(DateTime.Today.Year, 1, 1),
Maximum = new DateTime(DateTime.Today.Year, 12, 31),
Spoken = () => "Due",
};A field that holds text it cannot read — 12a in a number field — shows that as its own validation message until the text reads again.
Validation
Any control can be wrong. A control with an Error text is in the Invalid state: the theme frames it in red and marks it, the message is its tooltip and its screen-reader help text, and a reader hears it when it appears while the control has the focus.
// Set by the application ...
var name = new TextBox { Id = "name", Spoken = () => "Name" };
name.Error = "Please enter a name."; // null or "" clears it
// ... or taken from a model that implements INotifyDataErrorInfo or IDataErrorInfo.
TextBox? mail = null;
mail = new TextBox { Id = "mail", Spoken = () => "E-mail", Changed = () => model.Email = mail!.Text };
mail.BindErrors(model, nameof(SignUp.Email));BindErrors follows the model from then on, on any thread; the message is set on the UI thread and only the control repaints. How it looks is a style rule like any other: Styling.
Menus, toolbars and context menus
A MenuBar opens its menus as panes; F10 goes to the bar, Alt and the underlined letter (&File) opens a menu from anywhere in the tree, Left and Right walk the menus. The entries are asked for when a menu opens, so they may depend on the state. Any control takes a ContextMenu, opened by the right button or Shift+F10, and a Tooltip.
var menus = new MenuBar(
new MenuBarItem("&File", () =>
[
new MenuItem("New", () => Log("new"), Shortcut: "Ctrl+N"),
new MenuItem("Save", Save, Shortcut: "Ctrl+S"),
MenuItem.Separator(),
new MenuItem("Print...", () => Log("print")),
]),
new MenuBarItem("&View", () =>
[
new MenuItem("Bold text", () => bold = !bold, LiveChecked: () => bold, ClosesMenu: true),
]))
{ Id = "menubar" };
var tools = new ToolBar { Id = "toolbar", AccessibleName = () => "Formatting" }
.Add(new Button { Id = "save", Text = () => "Save", Click = Save, Tooltip = () => "Save the document" })
.Separator()
.Add(new CheckBox { Id = "bold", Text = () => "Bold", Value = () => bold, Toggle = () => bold = !bold });
var note = new Label
{
Text = () => "Right-click for the note's menu.",
ContextMenu = () =>
[
new MenuItem("Copy note", () => Log("copy")),
MenuItem.Separator(),
new MenuItem("Delete note", () => Log("delete"), Danger: true),
],
};Images
var logo = ArionBitmap.FromFile("logo.png"); // decoded once, when it is made
var picture = new ArionImage
{
Source = logo,
Stretch = ImageStretch.Fit,
Height = 90,
AltText = () => "Company logo",
};An ArionBitmap is decoded once when it is made and keeps its pixels for as long as it lives, so no frame decodes it; the GPU uploads them within its own resource cache. ImageEl draws a bitmap inside a cell template or a card.
What every control has
Id- Names the control for focus (
initialFocusId), for the dispatch and for tests. A control without one gets an id from its position. AccessibleName,Spoken- What a screen reader calls it, when its own text is not enough.
Tooltip,ContextMenu- A text shown when the pointer rests on the control, and the entries of its context menu — both asked for each time.
Error,ValidationMessage- What is wrong with the value, set by the application; the message the control shows, its own reading of the input first.
EnabledWhen,VisibleWhen- Asked each time; a disabled control takes no input and gets the
Disabledstate for the style sheets. Classes- The control's style classes, which the rules of the sheets select. See Styling.
ExplainStyle(states)- What the cascade weighed for the control's face in those states.
Focus, keyboard and screen readers
A ControlHost holds a tree of controls: focus follows the click, Tab walks the tree in order, the pointer is captured while a button is held, and the focused control draws its focus ring. ControlDispatch carries keys, text, the clipboard and the caret in from the host, and lets Tab move into and out of the tree from the window around it. Each control has a role — button, text, check box, radio button and group, combo box, spin button, date picker, slider, tab list and tab, menu item, image, static text, group, table — and a value where it has one; the hosts expose them to screen readers — UI Automation on Avalonia and WPF, MSAA on WinForms. The candidate window of an input method is placed at the caret; text being composed is not shown in the field (no IME pre-edit).
A drop-down button
A DropDownButton opens what the application gives it. With MenuOverlayContent that is a menu, opened as a pane of the surface that shows the button:
using ArionUI.Presentation.Overlay; // MenuOverlayContent, MenuItem, OverlayPlacement
var pick = new DropDownButton
{
Text = () => region,
Open = anchor => surface.OpenPane(
new MenuOverlayContent(
[
new MenuItem("North", () => region = "North"),
new MenuItem("South", () => region = "South"),
MenuItem.Separator(),
new MenuItem("All regions", () => region = "All"),
],
surface.MeasureText),
anchor,
OverlayPlacement.BelowStart),
};Panes open in a stack with light dismiss: a click outside closes them. The same pane stack carries the grid's own menus, the calendar, the combo lists and the filter lists. For a field that holds a value, use a ComboBox instead.
Drawing your own
var gauge = new Drawing
{
Height = 48,
Paint = (s, r) =>
{
s.DrawRoundedRect(r, 6, Palette.HeaderFill, Rgba.Transparent, 0);
s.DrawRoundedRect(r with { Width = r.Width * 0.62 }, 6, Palette.Accent, Rgba.Transparent, 0);
},
AccessibleName = () => "Load 62 percent",
};Palette reads the current theme, so the drawing follows a theme switch. For a micro chart there is no need to draw: ElementTile shows a column's cell element on its own, with the tooltip the column has in a table.
var spark = new ElementTile(
Column.Sparkline<IReadOnlyList<double>>("Revenue", h => h, v => v.ToString("N1") + " k"),
history)
{
Height = 44,
};Controls go on a board, into a pane, or — outside any grid — onto an ArionControlSurface in a WinForms, WPF or Avalonia window.
Recently built
The controls on this page that the plan of 4 October 2026 still listed as missing. Not built: a native WinForms or WPF control inside a tile, floating panels and a designer — see What it does not do yet.
Built Recently built
- Tab control Almost every business form groups its fields on tabs.
- Radio buttons and option groups An exclusive choice with arrow keys and the right screen-reader role, not faked with check boxes.
- A combo box: a value with type-ahead, or free text with suggestions A form field needs a value it holds and a list you can type into.
- Multi-line text box Notes, comments and addresses do not fit on one line.
- Numeric up-down and date picker The editors the grid has in its cells, now as form fields, with formats and masks from the culture.
- Menu bar, toolbar and context menus on controls A window needs a menu bar at its top edge, with F10 and access keys, and a context menu on any control.
- Image control Logos, photos and icons, decoded once instead of on every frame.
- Tooltips on controls A button with only an icon needs a tooltip to explain itself.
- A validation state on controls: an error text and an Invalid state for style sheets A form shows which field is wrong and why, in the theme's colours, and a screen reader hears it.
Everything the plan of 4 October 2026 listed is built. The roadmap shows what comes now, next and later, what is built and what is not planned.



