mirror of
https://github.com/saymrwulf/xous-core.git
synced 2026-11-12 07:44:18 +00:00
Really clear up the roles and structures of word wrapping. Significantly, we have now figured out that the word wrapper should be the word wrapper, and that the text bounds should be computed by a text bounds computation. Conflating flexible text bounds with word wrapping makes the math really hard. So, the word wrapper always works with a bounding area starting at 0,0, and will wrap until it hits a Point designated as its absolute max bounds. The returned typeset block is referenced to 0,0, and then it is shifted to the correct location by the rendering function. This externalizes the computation of the final location plus the rendering bounds to the outer functions that need to care about this, thus simplifying the word wrapper significantly. |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||