aboutsummaryrefslogtreecommitdiffstats
path: root/docs/scripting.md
diff options
context:
space:
mode:
authoruser <user@clank>2026-09-29 14:25:34 +0200
committeruser <user@clank>2026-09-29 14:25:34 +0200
commit3760c4e99aff06d09edb0575d7596d0607298e71 (patch)
treec6e1a676cdccb449e1f59309dd622bd14a7bb544 /docs/scripting.md
parentskill: the verbs that shipped since, and the bare form's other shape (diff)
downloadslosh-3760c4e99aff06d09edb0575d7596d0607298e71.tar.gz
slosh-3760c4e99aff06d09edb0575d7596d0607298e71.tar.xz
slosh-3760c4e99aff06d09edb0575d7596d0607298e71.zip
mouse: encode pixel reports against the cell size we advertise
A pane is told how big a cell is twice -- in mode 2048's resize report and in the XTWINOPS answers -- and the mouse encoder was told something else: a 1x1 cell, so that cell coordinates and "pixels" were the same number. That held until a program turned on SGR-pixel mouse (mode 1016) by itself. Textual does, the moment in-band resize works, and then divides every coordinate it is sent by the pixels-per-cell we advertised: a click 30 cells across and 9 down arrived as (3, 0), so every click in a Textual app landed in the top-left corner. Hand the encoder the cell size the pane already has, and put the pointer in the middle of its cell. A size that contradicts what the same pane was told about itself is the lie, not the precision.
Diffstat (limited to 'docs/scripting.md')
0 files changed, 0 insertions, 0 deletions