← back to pin list

7e. Units — per-user display units, unit-suffix input everywhere, inches stay the internal truth

kerfmaster pin list · UI / workflow decisions

rulingA decision by Aristide or Jordan. True because it was decided; it can be superseded, but it cannot be stale.

Content last changed 2026-08-19 — computed from the item itself, not typed.

Contract — Cross-cutting stage

This contract states a decision, not an implementation.

takes

makes

fails if Letting a display-unit preference leak into stored geometry, table values or posted NC; a field that accepts only the session unit.

Contract last changed 2026-08-19 — computed, not typed. Dated separately from the text above, so neither date can speak for the other.

Ruled by Aristide 2026-08-19 (sitting answers part 2, /design/answers/, verbatim there): per-user working units switchable Adobe-style; mixed-unit teams are the design case ('I think in inches but my colleague thinks in millimeters'); every numeric input accepts a suffix (3mm, 0.125in) and converts on entry, exactly as Illustrator accepts 3pt or 3mm anywhere. Also ruled in the same breath: configurable keyboard-nudge notches in preferences. Implementation constraint recorded, not yet built: parsing lives at the input boundary, conversion is immediate, and everything downstream — geometry, tables (materials/machine values keep their native inch provenance), G-code — remains in inches with the existing 4-decimal emit floor. Display formatting per unit is a rendering concern. The existing intake unit-DETECTION rules (INSUNITS etc.) are untouched — this pin is about human input, not file input.