Foundation

Interaction results

Share handled, changed, activation, rejection, focus, and capture results.

Generated previewCharm
Dedicated Interaction results example rendered in the Charm skin

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

When to use it

Use the common result vocabulary when an application coordinates several components without callbacks.

State and ownership

The Flyology_TUI.Components.Interactions package defines this component.

A component update result is a detached value. Capture actions explicitly acquire or release application-owned mouse capture.

  • An interaction result is a detached value.
  • The application owns focus and mouse capture and applies the requested capture action.

Input and updates

Applications inspect the result after Update, mutate their own domain state, then schedule another render.

Integration sequence

  1. Receive Update_Result from an interactive component handler; this package defines the result vocabulary rather than a handler of its own.
  2. Inspect handled, changed, activated, rejected, focus, and capture fields and apply the requested application-owned state changes.
  3. Present the next frame from the updated component and application state.

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.