Generated reference › API — ICoreEssentials/UI/Layouts
kind: generated#api#icoreessentials-ui-layouts

API — ICoreEssentials/UI/Layouts

The public contract of 2 header(s) under src/ICoreEssentials/UI/Layouts — 0 class/struct definition(s), 0 declaration(s). Each section shows the header's banner and its public (and protected-virtual) surface exactly as the file writes it.

HeaderDefinesDeclarationsBases
ICoreFlowLayout.h0
ICoreLayouts.h0

ICoreFlowLayout.h#

src/ICoreEssentials/UI/Layouts/ICoreFlowLayout.h

Declares no class of its own — see the file.

ICoreLayouts.h#

src/ICoreEssentials/UI/Layouts/ICoreLayouts.h

ICoreVBoxLayout / ICoreHBoxLayout / ICoreGridLayout / ICoreStackedLayout / ICoreFormLayout -- the editor's box, grid, stack and form layouts.

Styled subclasses (README S9, shape 1) of the five Qt layouts, and the only family in this folder with NO applyTheme(). That is a finding rather than an omission, and it is worth stating because a component without a theme hook otherwise reads as one that forgot it (README S3, and C6 made the same argument for the native dialogs):

A layout has no colour. It has no paint event either -- it moves other widgets and draws nothing itself. And the theme this project switches is a COLOUR theme: ICoreTheme carries fills, borders, text and shadow tones and not one metric, so there is no token for a layout to re-read on a Light <-> Dark switch. Subscribing to themeChanged here would install a

File-scope declarations#

// Shared by all five, so a call site does not have to remember which layout's
// enum it is naming. Deliberately not nested in one of them: nesting would
// make `ICoreVBoxLayout::Fit` the spelling at an ICoreGridLayout call site.
enum class ICoreLayoutFit {
    Default,   // Qt's own margins and spacing -- untouched
    Tight      // contents margins 0, spacing 0
};