scaled

The same measurements, every one of them multiplied by factor.

Metro's numbers were drawn for a 480 px phone, and at the canonical 0.75 they land on a 360 dp canvas. On a larger window — a desktop, a tablet — the 9 dp page margin that felt right there reads as cramped, and adjusting it alone would break its relationship with the tile gap, which is the same 12 Metro pixels. So the scale is one knob over the whole set: everything moves together or nothing does.

The type ramp scales with it, and scale is what carries that to KvadrantTheme, which applies it to KvadrantTypography. This used to say the opposite — that text has its own reason to be the size it is and scaling both at once turns a faithful layout into a merely large one. That is the Android and iOS convention and it is not Metro's: the phone's canvas was 480 units wide whatever the screen was, text was measured in those same units as everything else, and the device stretched the whole of it (×1.5 on 720p, ×1.6 on WXGA, ×2.25 on 1080p). A 20-unit body line was 2.18 mm on a 4-inch Lumia 520 and 3.11 mm on a 6-inch Lumia 1520. Research §1.6c.

tiltDepression is not scaled either, and that one is a measurement rather than a taste. It reads as the obvious omission — every other screen distance here scales, so surely a press should sink further on a scaled-up tile — but the tilt is already proportional without any help. The depression is a push along z, and what reaches the screen is depth / (depth + depression), a ratio with no term in it for the size of the thing being pressed: at the default numbers every surface, from a 24 dp checkbox to a 210 dp tile, draws at 0.9685 of itself. Scaling the depression does not make a big tile sink more in proportion — it makes it sink more than a small one, which is the defect, not the fix. TiltScaleInvarianceTest fails if this line acquires a * factor.

The same ramp, every size multiplied by factor.

Windows Phone scaled its text with its layout and this restores that. The canvas was 480 units wide whatever the screen was, and the device stretched the whole of it — ×1.5 on 720p, ×1.6 on WXGA, ×2.25 on 1080p — so a 20-unit body line was physically 2.18 mm on a 4-inch Lumia 520 and 3.11 mm on a 6-inch Lumia 1520. Text was measured in the same units as margins and tiles and had no way not to scale with them.

Leaving the ramp fixed while the layout grows is the Android and iOS convention, and it was this project's until it was checked: research §1.6c has the measurements. Nothing is rounded to whole sp on the way — Metro's own ramp is not whole numbers either (18.667, 22.667, 25.333 px), and rounding a scaled ramp would break the relationships the unrounded one holds.