Class UnitType

Field Details

• AXIS_X

  public static final int AXIS_X

  Axis constant for a horizontal, i.e. X, evaluation pass.

  See Also:

  • Constant Field Values

• AXIS_Y

  public static final int AXIS_Y

  Axis constant for a vertical, i.e. Y, evaluation pass.

  See Also:

  • Constant Field Values

• UT_PX

  public static final int UT_PX

  Pixels, px. The identity scale of 1.0; the emitter emits no scale opcode for it, and it is the implicit unit of a bare number.

  See Also:

  • Constant Field Values

• UT_PT

  public static final int UT_PT

  Points, pt, i.e. 1/72 inch.

  See Also:

  • Constant Field Values

• UT_EM

  public static final int UT_EM

  The font size of the element's own font, em. Per-element.

  See Also:

  • Constant Field Values

• UT_EX

  public static final int UT_EX

  The x-height of the element's own font, ex. Per-element.

  See Also:

  • Constant Field Values

• UT_DLG

  public static final int UT_DLG

  Dialog units, dlg. Axis-dependent, and per-element since it depends on the element's own font. Windows dialog units use a different base unit AND a different divisor per axis: horizontal px = dlu*baseUnitX/4, vertical px = dlu*baseUnitY/8.

  See Also:

  • Constant Field Values

• UT_PC

  public static final int UT_PC

  Percent of the parent along the axis being calculated, %. Axis-dependent.

  See Also:

  • Constant Field Values

• UT_PCW

  public static final int UT_PCW

  Percent of the parent WIDTH, %w. Axis-independent, so it is usable on the Y axis to obtain an X-relative value.

  See Also:

  • Constant Field Values

• UT_PCH

  public static final int UT_PCH

  Percent of the parent HEIGHT, %h. Axis-independent, the mirror of UT_PCW.

  See Also:

  • Constant Field Values

• UT_PCMIN

  public static final int UT_PCMIN

  Percent of the SMALLER of the parent's width and height, %min. Axis-independent: the same value on the X pass and the Y pass.

  See Also:

  • Constant Field Values

• UT_PCMAX

  public static final int UT_PCMAX

  Percent of the LARGER of the parent's width and height, %max. Axis-independent.

  See Also:

  • Constant Field Values

• UT_VW

  public static final int UT_VW

  Percent of the viewport width, vw.

  See Also:

  • Constant Field Values

• UT_VH

  public static final int UT_VH

  Percent of the viewport height, vh.

  See Also:

  • Constant Field Values

• UT_VMIN

  public static final int UT_VMIN

  Percent of the smaller viewport dimension, vmin.

  See Also:

  • Constant Field Values

• UT_VMAX

  public static final int UT_VMAX

  Percent of the larger viewport dimension, vmax.

  See Also:

  • Constant Field Values

• UT_NL

  public static final int UT_NL

  The safe-area inset on the LEFT, nl.

  See Also:

  • Constant Field Values

• UT_NR

  public static final int UT_NR

  The safe-area inset on the RIGHT, nr.

  See Also:

  • Constant Field Values

• UT_NW

  public static final int UT_NW

  The notch cutout bounding-box WIDTH in SCREEN space, nw.

  The meaning of this unit is restated. It is the screen-space width of the cutout, not "the maximum of the left and right insets" as the original javadoc said. Because nw and UT_NH describe the bounding box in screen space, they swap as the device rotates under the cutout: a 40x10 notch in portrait becomes 10x40 in landscape, and a formula author never has to branch on orientation.

  In landscape the two descriptions coincide, since the inset perpendicular to the edge IS the cutout extent along the screen's horizontal; that is why the previous definition worked in practice. In portrait the width has no data source on the web platform and resolves to whatever the IScaleProvider reports, which is 0 unless a measured value has been supplied.

  See Also:

  • Constant Field Values

• UT_NT

  public static final int UT_NT

  The safe-area inset on the TOP, nt.

  See Also:

  • Constant Field Values

• UT_NB

  public static final int UT_NB

  The safe-area inset on the BOTTOM, nb. Note that in portrait on an iPhone X or later this is the home-indicator inset, around 34px, and NOT zero.

  See Also:

  • Constant Field Values

• UT_CWMIN

  public static final int UT_CWMIN

  The component's own computed CSS min-width in pixels, cwmin.

  Naming. %min, %max, %w and %h all measure the PARENT; these four measure the COMPONENT. Naming them %wmin and so on would put two different subjects under one prefix, so that %w and %wmin would read as a family while meaning different things. The c prefix marks the subject.

  See Also:

  • Constant Field Values

• UT_CWMAX

  public static final int UT_CWMAX

  The component's own computed CSS max-width in pixels, cwmax. See UT_CWMIN for the naming.

  See Also:

  • Constant Field Values

• UT_CHMIN

  public static final int UT_CHMIN

  The component's own computed CSS min-height in pixels, chmin. See UT_CWMIN for the naming.

  See Also:

  • Constant Field Values

• UT_CHMAX

  public static final int UT_CHMAX

  The component's own computed CSS max-height in pixels, chmax. See UT_CWMIN for the naming.

  See Also:

  • Constant Field Values

• UT_REM

  public static final int UT_REM

  The ROOT element font size, rem. Real CSS and universally supported; UT_EM covers the element's own font, nothing else was root-relative.

  See Also:

  • Constant Field Values

• UT_DPX

  public static final int UT_DPX

  ONE PHYSICAL DEVICE PIXEL expressed in CSS pixels, dpx, i.e. 1/devicePixelRatio. A LENGTH.

  0.333px on a 3x display and 0.25px at 4x, so on a 4x device 4dpx is exactly 1px. Non-integer ratios are the common case, since Windows display scaling gives 1.25, 1.5, 1.75 and 2.5, and they work normally: 1dpx at 1.25 is 0.8px.

  Two caveats. First, browsers re-round hairlines: for border-width, outline-width, column-rule-width and outline-offset the computed length is rounded to an integer number of device pixels, so a dpx-derived value landing in one of those four properties gets the browser's rounding applied on top of ours. Width, height, margin and padding pass through untouched. Second, devicePixelRatio is not constant for the life of a page: it changes on browser zoom and when a window moves between displays of different density, with NO resize event, so the client must refill this slot from a matchMedia('(resolution: Ndppx)') change listener.

  Neither dpx nor UT_DPR is a CSS unit. CSS has no <length> unit for a physical device pixel; dppx exists but is a <resolution> unit valid only inside media queries. This is no different from dlg, %w or nl in that the browser only ever receives the evaluated px value.

  See Also:

  • Constant Field Values

• UT_DPR

  public static final int UT_DPR

  THE DEVICE PIXEL RATIO ITSELF, dpr: 1, 1.25, 1.5, 2, 3.

  This unit is unlike every other one. Every other unit is a measurement that stands alone. dpr is a bare MULTIPLIER, NOT A LENGTH: 1dpr by itself resolves to an arbitrary pixel count, 3px on a 3x display, and is not a meaningful size. It is only useful multiplied by something else, e.g. 16px*1dpr which gives 48px there. It is intended for density-aware sizing.

  dpr and UT_DPX are exact reciprocals, so 1dpx*1dpr is exactly 1px in IEEE double even at 3x, since (1.0/3.0)*3.0==1.0. They can therefore cancel silently in a formula.

  Do not confuse the IIZI unit dpr with the JavaScript variable window.devicePixelRatio. They are the same quantity at different layers: the unit is what a designer writes in a formula, the variable is what fills the scale table.

  See Also:

  • Constant Field Values

• UT_NH

  public static final int UT_NH

  The notch cutout bounding-box HEIGHT in SCREEN space, nh. Pairs with UT_NW; see there for the screen-space rotation behaviour.

  See Also:

  • Constant Field Values

• UT_NX

  public static final int UT_NX

  The offset along the top or bottom edge to the LEFT side of the notch, nx. Used mainly in portrait and zero in landscape.

  EDGE, not centre. nx is the left edge, nx+nw the right edge, and the centre is nx+nw/2 when wanted. Centre-based offsets would make the common case pay a -nw/2 tax, and edge is consistent with nl, nr, nt and nb and with every platform API, all of which return rectangles. A useful expression worth knowing rather than adding a unit for: the gap to the right of the notch in portrait is 100%w-(1nx+1nw).

  See Also:

  • Constant Field Values

• UT_NY

  public static final int UT_NY

  The offset along the left or right edge to the TOP of the notch, ny. Used mainly in landscape and zero in portrait. See UT_NX for the edge-not-centre decision.

  See Also:

  • Constant Field Values

• UNIT_COUNT

  public static final int UNIT_COUNT

  The number of unit types, i.e. the largest legal UT_* value.

  See Also:

  • Constant Field Values

• SCALE_TABLE_SIZE

  public static final int SCALE_TABLE_SIZE

  The size of a scale table, i.e. UNIT_COUNT+1 since the table is indexed one-based by the UT_* constants and slot 0 is unused.

  See Also:

  • Constant Field Values