pub enum Strip {
Across,
Down,
}Expand description
Which way a Region::TabGroup’s strip runs.
Across is a row of tabs over the panes it opens; down is a column of them beside the panes. Both are the folder semantic, one pane showing at a time, and both put the strip first, so a tab is always read before the pane it opens.
§Why the description says it
Leaving it to each renderer was the earlier reading, and the measurement ran the other way: every renderer picked across, so a tab group that wanted a column had no way to get one. MNW’s settings sections were a column beside their panes until they were described, and describing them flattened them into a row. Counted on the MNW dashboards (2026-09-12): five strips run across, one runs down today, four long panels want a strip down beside their sections, and two screens carry both. Max’s ruling is that the language says both.
§What is here and what is not
The direction, carried beside the region the way Showing is: this crate
names the fact and the holder of the region states it, because the region
member is a place and not a record of how it is dressed.
No default. A tab group that says nothing about its strip is the silence this type exists to end, so a holder has to pick one.
No breakpoint. Room is still the renderer’s to measure. A strip that runs down may fold over its panes when there is no room beside them, the way a row folds into a menu; what it may not do is run across when there is room, because then the description stopped being what was drawn.
Variants§
Implementations§
Source§impl Strip
impl Strip
Sourcepub const fn runs_down(self) -> bool
pub const fn runs_down(self) -> bool
Whether the tabs stack vertically.
What a renderer asks for the two things that turn on direction rather
than on placement: the accessibility orientation a strip announces, and
which pair of arrow keys moves between its tabs. A method for
Region::name’s reason, so three renderers do not each write the
comparison.