summaryrefslogtreecommitdiff
path: root/test/kill.script
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-11-17 09:29:57 -0300
committerGabriel Schneider <[email protected]>2026-11-17 12:15:01 -0300
commit7ad16df2813c0c3012bae6262014b07b7bc7277d (patch)
treea144817721d20308f8bd0b0b8531c5c9bfa6b383 /test/kill.script
parentecdb435ce789ed81d0edfaf25268848ae1e57442 (diff)
downloadsketchbook-7ad16df2813c0c3012bae6262014b07b7bc7277d.tar.gz
sketchbook-7ad16df2813c0c3012bae6262014b07b7bc7277d.zip
text: sk.text.places, every byte's place in one layout
An editor draws a range under its bytes, a caret on its glyph, a mark under a byte, and finds the byte under the pointer; with mixed sizes on a line a column is no longer a measure. `layout`'s `caret` gives one byte's place a layout, so a range, a caret and a hit test were a layout a byte. `sk.text.places(bytes, paragraph, out)` is the same layout with every byte's place in `out` (where a caret before that byte sits, a `Caret`: x, the line's top and height; a `\n` and the spaces a line wraps at are at its end, and one more for the end of the text). The byte at a point is then a loop over places: the last whose line holds its y and whose x is at or left of it. `lay` takes the slice to fill (empty: none), so `layout`, `places` and `f.paragraph` stay one function. Pure, as `layout`: in `update` too. The README's editor recipe and docs/text.md say so. Test: a paragraph's places are where its caret sits, byte by byte (wrapped at a space, a `\n`, a span twice the size, a two-byte codepoint, a last empty line). zig build test-text: 52 of 52 steps. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_016Y9MNBECMWcJD5pdS4SR6T
Diffstat (limited to 'test/kill.script')
0 files changed, 0 insertions, 0 deletions