Skip to main content

Module widget

Module widget 

Source
Expand description

The described things that are not fields, tables or frames.

A meter, a token, a control, a figure. makeover-tui has had these since its own widget module and this crate has not, which is the gap that showed up the moment anything tried to draw a whole quasi_router::Screen in egui: the screen walk had a renderer for the containers and nothing for four of the nodes inside them, so the drawing would have landed in the consumer, one copy per app. That is the divergence this suite exists to end, so it lands here.

§What “in egui” changes, and what it does not

The semantics are makeover-tui’s, deliberately: a meter is a bar and a reading, a badge is round and a chip is square, a control names its key where the description gave one, and a figure puts the movement on the value rather than on the caption. Those are description-level readings and they do not get a second opinion per host.

What differs is forced by the target rather than chosen. A terminal spends a whole cell on a character and returns a Line for the caller to place; egui paints an arbitrary rect and answers a Response, so every function here draws into the Ui it is given and hands back what the user did to it. That is also why nothing here takes a focused flag the way makeover-tui’s act does: egui owns focus, which is the rule the crate header states.

Structs§

WidgetStyle
The sizes a widget cannot derive from the description.

Functions§

act
A control.
figure
A figure: the value, then what it counts under it.
meter
A proportion as a bar and a reading.
token
A badge or a chip.