2D vector (often used to store positions or sizes)

4D vector (often used to store floating-point colors)

Simple class to represent JSON object

Helper: ImVec2ih (2D vector, half-size integer, for long-term packed storage)

Simplified structure to mimic a Document model

in_place_t Tag type used to specify in-place construction, such as with `phmap::optional`, designed to be a drop-in replacement for C++17's `std::in_

Runtime data for multiple fonts, bake multiple fonts into a single texture, TTF/OTF font loader

@brief exception indicating access out of the defined range @sa https://json.nlohmann.me/api/basic_json/out_of_range/

Helper: ImVec1 (1D vector) (this odd construct is used to facilitate the transition between 1D and 2D, and the maintenance of some branches/patches)

Helper to build glyph ranges from text/string data

Storage for one type registered in the .ini file

Temporary storage for one window (that's the data which in theory we could ditch at the end of the frame)

! Input adapter for a (caching) istream. Ignores a UFT Byte Order Mark at beginning of input. Does not support changing the underlying std::streambuf

Forward declarations

Temporary storage to output draw commands out of order, used by ImDrawListSplitter and ImDrawList::ChannelsSplit()

All draw command lists required to render the frame + pos/size coordinates to use for the projection matrix.

Helper to build a ImDrawData instance

Storage data for a single column

Backup and restore IsItemHovered() internal data

Storage for a tab bar

Storage for a tab item (within a tab bar)

! Input adapter for stdio file access. This adapter read only 1 byte and do not use any buffer. This adapter is a very low level adapter. */

Column major 4x4 matrix to match GLM TODO: swap to 3x4 row-major to match other backends

@brief an iterator for primitive JSON types This class models an iterator for primitive JSON types (boolean, number, string). It's only purpose is to

A simple arcball camera that moves around the camera's focal point. * The mouse inputs to the camera should be in normalized device coordinates, * w

------------------------------------------------------------------------ ------------------------------------------------------------------------

f(t1, t2, ..., tN) in all other cases.