1. Flyology TUI
  2. Components
  3. Check boxes

Controls

Check boxes

Represent unchecked, checked, and mixed boolean state.

Generated previewCharm
Dedicated Check boxes example rendered in the Charm skin

The site build compiles the dedicated Ada component example, constructs Check boxes through its public API, and exports that exact styled surface. Read the capture source.

When to use it

Use a check box for an independent option. Use a radio group when exactly one choice must remain active.

State and ownership

The Flyology_TUI.Components.Check_Boxes package defines this component.

The model retains tri-state value and interaction state. Programmatic setters cancel stale activation without losing pending release ownership.

  • The application model owner applies updates during serial event dispatch.
  • Appearance and skin values are borrowed only while the component renders.

Input and updates

Space toggles the focused value. A mouse gesture toggles only after a matching release.

Integration sequence

  1. Create the bounded model and populate it with caller-owned data.
  2. Route the current keyboard or local mouse event through the component handler.
  3. Apply the typed result, then render from the updated model with the current appearance.

See the linked package reference for its exact declarations and contracts.

Responsive and accessible behavior

  • Use dimensions and regions from the current layout or presentation value.
  • When a component owns mouse capture, route its matching release even when the pointer leaves the original bounds.
  • Retain a glyph, label, border, or text-attribute cue when the terminal reduces color.